Project

General

Profile

Bug #19112

rgw_file: RGWFileHandle dtor must also cond-unlink from FHCache

Added by Matt Benjamin 9 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
03/01/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
jewel kraken
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Release:
Needs Doc:
No

Description

Formerly masked in part by the reclaim() action, direct-delete now substitutes for reclaim() iff its LRU lane is over its high-water mark, and in particular, like reclaim() the destructor is certain to see handles still interned on the FHcache when nfs-ganesha is recycling objects from its own LRU.


Related issues

Copied to rgw - Backport #19418: jewel: rgw_file: RGWFileHandle dtor must also cond-unlink from FHCache Resolved
Copied to rgw - Backport #19471: kraken: rgw_file: RGWFileHandle dtor must also cond-unlink from FHCache Resolved

History

#1 Updated by Ken Dreyer 8 months ago

  • Status changed from In Progress to Pending Backport

#2 Updated by Ken Dreyer 8 months ago

  • Copied to Backport #19418: jewel: rgw_file: RGWFileHandle dtor must also cond-unlink from FHCache added

#3 Updated by Nathan Cutler 8 months ago

  • Copied to Backport #19471: kraken: rgw_file: RGWFileHandle dtor must also cond-unlink from FHCache added

#4 Updated by Nathan Cutler 4 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF