From: Ilya Dryomov <idryomov@gmail.com>
To: Xiubo Li <xiubli@redhat.com>
Cc: Venky Shankar <vshankar@redhat.com>,
ceph-devel@vger.kernel.org, jlayton@kernel.org,
mchangir@redhat.com, lhenriques@suse.de, stable@kernel.org,
Patrick Donnelly <pdonnell@redhat.com>
Subject: Re: [PATCH] ceph: flush cap release on session flush
Date: Tue, 7 Feb 2023 17:03:32 +0100 [thread overview]
Message-ID: <CAOi1vP9sPucujJrKxy6+-7nGh90VVGtWNrPsZsH5psVW-tcDNA@mail.gmail.com> (raw)
In-Reply-To: <f31e08f5-972b-f29c-926a-2586863965f5@redhat.com>
On Tue, Feb 7, 2023 at 6:19 AM Xiubo Li <xiubli@redhat.com> wrote:
>
>
> On 07/02/2023 13:16, Venky Shankar wrote:
> > On Tue, Feb 7, 2023 at 10:35 AM <xiubli@redhat.com> wrote:
> >> From: Xiubo Li <xiubli@redhat.com>
> >>
> >> MDS expects the completed cap release prior to responding to the
> >> session flush for cache drop.
> >>
> >> Cc: <stable@kernel.org>
> >> URL: http://tracker.ceph.com/issues/38009
> >> Cc: Patrick Donnelly <pdonnell@redhat.com>
> >> Signed-off-by: Xiubo Li <xiubli@redhat.com>
> >> ---
> >> fs/ceph/mds_client.c | 6 ++++++
> >> 1 file changed, 6 insertions(+)
> >>
> >> diff --git a/fs/ceph/mds_client.c b/fs/ceph/mds_client.c
> >> index 3c9d3f609e7f..51366bd053de 100644
> >> --- a/fs/ceph/mds_client.c
> >> +++ b/fs/ceph/mds_client.c
> >> @@ -4039,6 +4039,12 @@ static void handle_session(struct ceph_mds_session *session,
> >> break;
> >>
> >> case CEPH_SESSION_FLUSHMSG:
> >> + /* flush cap release */
> >> + spin_lock(&session->s_cap_lock);
> >> + if (session->s_num_cap_releases)
> >> + ceph_flush_cap_releases(mdsc, session);
> >> + spin_unlock(&session->s_cap_lock);
> >> +
> >> send_flushmsg_ack(mdsc, session, seq);
> >> break;
> > Ugh. kclient never flushed cap releases o_O
>
> Yeah, I think this was missed before.
Now queued up for 6.2-rc8.
Thanks,
Ilya
next prev parent reply other threads:[~2023-02-07 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 5:04 [PATCH] ceph: flush cap release on session flush xiubli
2023-02-07 5:16 ` Venky Shankar
2023-02-07 5:19 ` Xiubo Li
2023-02-07 16:03 ` Ilya Dryomov [this message]
2023-02-07 12:48 ` Jeff Layton
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=CAOi1vP9sPucujJrKxy6+-7nGh90VVGtWNrPsZsH5psVW-tcDNA@mail.gmail.com \
--to=idryomov@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=jlayton@kernel.org \
--cc=lhenriques@suse.de \
--cc=mchangir@redhat.com \
--cc=pdonnell@redhat.com \
--cc=stable@kernel.org \
--cc=vshankar@redhat.com \
--cc=xiubli@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).