Project

General

Profile

Bug #40196

rgw_file: fix invalidation of top-level directories

Added by Matt Benjamin almost 5 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus, mimic, luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Originally, root_fh was reachable from RGWLibFS::fh_cache, but
this was problematic as it has infinite lifetime and so is not
present in RGWLibFS::fs_lru.

To fix the above, RGWLibFS::root_fh came to live unhooked from the
handle caches which works because nfs-ganesha/the application
always has an instance handle. However, this silently breaks
READDIR event invalidation.


Related issues

Copied to rgw - Backport #40214: luminous: rgw_file: fix invalidation of top-level directories Rejected
Copied to rgw - Backport #40215: mimic: rgw_file: fix invalidation of top-level directories Resolved
Copied to rgw - Backport #40216: nautilus: rgw_file: fix invalidation of top-level directories Resolved

History

#1 Updated by Matt Benjamin almost 5 years ago

  • Pull request ID set to 28440

#2 Updated by Matt Benjamin almost 5 years ago

  • Status changed from In Progress to Fix Under Review

#3 Updated by Matt Benjamin almost 5 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to nautilus, mimic, luminous

#4 Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40214: luminous: rgw_file: fix invalidation of top-level directories added

#5 Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40215: mimic: rgw_file: fix invalidation of top-level directories added

#6 Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40216: nautilus: rgw_file: fix invalidation of top-level directories added

#7 Updated by Nathan Cutler about 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF