Bug #46355
closedclient: directory inode can not call release_callback
0%
Description
I use Ganesha + CEPH to test release_callback feature, I have merged the relevant modification code:
https://github.com/ceph/ceph/pull/34596
https://github.com/nfs-ganesha/nfs-ganesha/commit/58a9114f6b2c48ffa4a04781bdf1faf3ca914f8d
https://github.com/nfs-ganesha/nfs-ganesha/commit/382966c1ce0298347d26a3d22a7c8988fdcdf1da
the test found that the directory inode could not be released,although it can be released in Ganesha, but it can not call _schedule_ino_release_callback() because its status is pinned.
Updated by Patrick Donnelly almost 4 years ago
- Status changed from New to Fix Under Review
- Assignee set to wei liu
- Target version set to v16.0.0
- Source set to Community (dev)
- Backport set to octopus,nautilus
- Pull request ID set to 35327
- ceph-qa-suite deleted (
fs) - Component(FS) Client added
Updated by Patrick Donnelly almost 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46516: octopus: client: directory inode can not call release_callback added
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46517: nautilus: client: directory inode can not call release_callback added
Updated by wei liu almost 4 years ago
Updated by Patrick Donnelly almost 4 years ago
wei liu wrote:
Hi Wei, the PR # is in the issue metadata. No need to leave a comment (it can cause confusion if the PR # changes!).
Updated by Nathan Cutler over 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".