From: Xiubo Li <xiubli@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: idryomov@gmail.com, ceph-devel@vger.kernel.org,
jlayton@kernel.org, vshankar@redhat.com, mchangir@redhat.com,
stable@vger.kernel.org
Subject: Re: [PATCH] ceph: remove the incorrect caps check in _file_size()
Date: Thu, 7 Sep 2023 08:14:05 +0800 [thread overview]
Message-ID: <43d88af6-9955-d65d-1949-c1b4ddec7070@redhat.com> (raw)
In-Reply-To: <2023090626-overgrown-probation-a58d@gregkh>
On 9/6/23 22:45, Greg KH wrote:
> On Wed, Sep 06, 2023 at 08:17:47PM +0800, xiubli@redhat.com wrote:
>> From: Xiubo Li <xiubli@redhat.com>
>>
>> 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'
>> caps.
>>
>> Cc: stable@vger.kernel.org
>> URL: https://tracker.ceph.com/issues/56693
>> Signed-off-by: Xiubo Li <xiubli@redhat.com>
>> ---
>> fs/ceph/inode.c | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
> What commit id does this fix?
Oh, I forgot to mention that in the commit comment, it will fix:
b0d7c2231015 ceph: introduce i_truncate_mutex
Let me update the patch and send out the V2 for it.
Thanks
- Xiubo
> thanks,
>
> greg k-h
>
prev parent reply other threads:[~2023-09-07 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 12:17 [PATCH] ceph: remove the incorrect caps check in _file_size() xiubli
2023-09-06 14:45 ` Greg KH
2023-09-07 0:14 ` Xiubo Li [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43d88af6-9955-d65d-1949-c1b4ddec7070@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=mchangir@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vshankar@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).