diff options
authorJeff Layton <>2020-05-20 10:36:07 -0400
committerIlya Dryomov <>2020-05-27 13:03:57 +0200
commitfb33c114d3ed5bdac230716f5b0a93b56b92a90d (patch)
parent890bd0f8997ae6ac0a367dd5146154a3963306dd (diff)
ceph: flush release queue when handling caps for unknown inode
It's possible for the VFS to completely forget about an inode, but for it to still be sitting on the cap release queue. If the MDS sends the client a cap message for such an inode, it just ignores it today, which can lead to a stall of up to 5s until the cap release queue is flushed. If we get a cap message for an inode that can't be located, then go ahead and flush the cap release queue. Cc: URL: Fixes: 1e9c2eb6811e ("ceph: delete stale dentry when last reference is dropped") Reported-and-Tested-by: Andrej Filipčič <> Suggested-by: Yan, Zheng <> Signed-off-by: Jeff Layton <> Signed-off-by: Ilya Dryomov <>
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/ceph/caps.c b/fs/ceph/caps.c
index 5f3aa4d607de..f1acde6fb9a6 100644
--- a/fs/ceph/caps.c
+++ b/fs/ceph/caps.c
@@ -3991,7 +3991,7 @@ void ceph_handle_caps(struct ceph_mds_session *session,
__ceph_queue_cap_release(session, cap);
- goto done;
+ goto flush_cap_releases;
/* these will work even if we don't have a cap yet */