Blob Blame History Raw
From: Xiubo Li <>
Date: Wed, 6 Sep 2023 14:22:07 +0800
Subject: ceph: fix incorrect revoked caps assert in ceph_fill_file_size()
Git-commit: 15c0a870dc44ed14e01efbdd319d232234ee639f
Patch-mainline: v6.6-rc6
References: bsc#1219445

When truncating the inode the MDS will acquire the xlock for the
ifile Locker, which will revoke the 'Frwsxl' caps from the clients.
But when the client just releases and flushes the 'Fw' caps to MDS,
for exmaple, and once the MDS receives the caps flushing msg it
just thought the revocation has finished. Then the MDS will continue
truncating the inode and then issued the truncate notification to
all the clients. While just before the clients receives the cap
flushing ack they receive the truncation notification, the clients
will detecte that the 'issued | dirty' is still holding the 'Fw'

Fixes: b0d7c2231015 ("ceph: introduce i_truncate_mutex")
Signed-off-by: Xiubo Li <>
Reviewed-by: Milind Changire <>
Signed-off-by: Ilya Dryomov <>
Acked-by: Luís Henriques <>

 fs/ceph/inode.c | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/fs/ceph/inode.c b/fs/ceph/inode.c
index 800ab7920513..b79100f720b3 100644
--- a/fs/ceph/inode.c
+++ b/fs/ceph/inode.c
@@ -769,9 +769,7 @@ int ceph_fill_file_size(struct inode *inode, int issued,
 			ci->i_truncate_seq = truncate_seq;
 			/* the MDS should have revoked these caps */
-					       CEPH_CAP_FILE_RD |
-					       CEPH_CAP_FILE_WR |
 			 * If we hold relevant caps, or in the case where we're