Project

General

Profile

Actions

Bug #46355

closed

client: directory inode can not call release_callback

Added by wei liu almost 4 years ago. Updated over 3 years ago.

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

0%

Source:
Community (dev)
Tags:
Backport:
octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Client, Ganesha FSAL
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

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.


Related issues 2 (0 open2 closed)

Copied to CephFS - Backport #46516: octopus: client: directory inode can not call release_callbackResolvedWei-Chung ChengActions
Copied to CephFS - Backport #46517: nautilus: client: directory inode can not call release_callbackResolvedNathan CutlerActions
Actions

Also available in: Atom PDF