From: Milind Changire <mchangir@redhat.com>
To: Venky Shankar <vshankar@redhat.com>
Cc: xiubli@redhat.com, ceph-devel@vger.kernel.org,
idryomov@gmail.com, jlayton@kernel.org
Subject: Re: [PATCH v3 0/2] ceph: fix caps revocation stuck
Date: Tue, 13 Feb 2024 15:03:49 +0530 [thread overview]
Message-ID: <CAED=hWCe9ZhCi3GOXTEU9JX4WA1BJK99Z_6dfr-Yn1x6iiba1A@mail.gmail.com> (raw)
In-Reply-To: <CACPzV1mfFu1wxeUXg2WU++8YsXe7gHz_Pk278sHQ=jOvEpLPTQ@mail.gmail.com>
On Mon, Feb 12, 2024 at 8:23 PM Venky Shankar <vshankar@redhat.com> wrote:
>
> On Wed, Jan 17, 2024 at 10:00 AM <xiubli@redhat.com> wrote:
> >
> > From: Xiubo Li <xiubli@redhat.com>
> >
> > V3:
> > - reuse the cap_wq instead of using the system wq
> >
> > V2:
> > - Just remove the "[1/3] ceph: do not break the loop if CEPH_I_FLUSH is
> > set" patch from V1, which is causing a regression in
> > https://tracker.ceph.com/issues/63298
> >
> >
> > Xiubo Li (2):
> > ceph: always queue a writeback when revoking the Fb caps
> > ceph: add ceph_cap_unlink_work to fire check_caps() immediately
> >
> > fs/ceph/caps.c | 65 +++++++++++++++++++++++++++-----------------
> > fs/ceph/mds_client.c | 48 ++++++++++++++++++++++++++++++++
> > fs/ceph/mds_client.h | 5 ++++
> > 3 files changed, 93 insertions(+), 25 deletions(-)
> >
> > --
> > 2.43.0
> >
>
> Tested-by: Venky Shankar <vshankar@redhat.com>
>
Reviewed-by: Milind Changire <mchangir@redhat.com>
> --
> Cheers,
> Venky
>
--
Milind
prev parent reply other threads:[~2024-02-13 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 4:27 [PATCH v3 0/2] ceph: fix caps revocation stuck xiubli
2024-01-17 4:27 ` [PATCH v3 1/2] ceph: always queue a writeback when revoking the Fb caps xiubli
2024-01-17 4:27 ` [PATCH v3 2/2] ceph: add ceph_cap_unlink_work to fire check_caps() immediately xiubli
2024-02-12 14:50 ` Venky Shankar
2024-02-12 14:53 ` [PATCH v3 0/2] ceph: fix caps revocation stuck Venky Shankar
2024-02-13 9:33 ` Milind Changire [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='CAED=hWCe9ZhCi3GOXTEU9JX4WA1BJK99Z_6dfr-Yn1x6iiba1A@mail.gmail.com' \
--to=mchangir@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.