From: Luis Henriques <lhenriques@suse.de>
To: Jeff Layton <jlayton@kernel.org>
Cc: "Yan, Zheng" <ukernel@gmail.com>,
Ilya Dryomov <idryomov@gmail.com>,
ceph-devel <ceph-devel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ceph: fix race in concurrent __ceph_remove_cap invocations
Date: Thu, 12 Nov 2020 14:45:18 +0000 [thread overview]
Message-ID: <87lff6d475.fsf@suse.de> (raw)
In-Reply-To: <2e81958e92563a568f2b9b5b4d23c4c7bab52f1c.camel@kernel.org> (Jeff Layton's message of "Thu, 12 Nov 2020 08:22:02 -0500")
Jeff Layton <jlayton@kernel.org> writes:
> On Thu, 2020-11-12 at 20:43 +0800, Yan, Zheng wrote:
>> On Thu, Nov 12, 2020 at 6:48 PM Luis Henriques <lhenriques@suse.de> wrote:
>> >
>> > A NULL pointer dereference may occur in __ceph_remove_cap with some of the
>> > callbacks used in ceph_iterate_session_caps, namely trim_caps_cb and
>> > remove_session_caps_cb. These aren't protected against the concurrent
>> > execution of __ceph_remove_cap.
>> >
>>
>> they are protected by session mutex, never get executed concurrently
>>
>
> Maybe not concurrently with one another, but the s_mutex is _not_ held
> when __ceph_remove_caps is called from ceph_evict_inode. We can't rely
> on it to protect this.
Hmm, yeah. I guess the changelog could mention that. Thanks, Jeff.
Cheers,
--
Luis
>> > Since the callers of this function hold the i_ceph_lock, the fix is simply
>> > a matter of returning immediately if caps->ci is NULL.
>> >
>> > Based on a patch from Jeff Layton.
>> >
>> > Cc: stable@vger.kernel.org
>> > URL: https://tracker.ceph.com/issues/43272
>> > Link: https://www.spinics.net/lists/ceph-devel/msg47064.html
>> > Signed-off-by: Luis Henriques <lhenriques@suse.de>
>> > ---
>> > fs/ceph/caps.c | 11 +++++++++--
>> > 1 file changed, 9 insertions(+), 2 deletions(-)
>> >
>> > diff --git a/fs/ceph/caps.c b/fs/ceph/caps.c
>> > index ded4229c314a..443f164760d5 100644
>> > --- a/fs/ceph/caps.c
>> > +++ b/fs/ceph/caps.c
>> > @@ -1140,12 +1140,19 @@ void __ceph_remove_cap(struct ceph_cap *cap, bool queue_release)
>> > {
>> > struct ceph_mds_session *session = cap->session;
>> > struct ceph_inode_info *ci = cap->ci;
>> > - struct ceph_mds_client *mdsc =
>> > - ceph_sb_to_client(ci->vfs_inode.i_sb)->mdsc;
>> > + struct ceph_mds_client *mdsc;
>> > int removed = 0;
>> >
>> > + /* 'ci' being NULL means he remove have already occurred */
>> > + if (!ci) {
>> > + dout("%s: cap inode is NULL\n", __func__);
>> > + return;
>> > + }
>> > +
>> > dout("__ceph_remove_cap %p from %p\n", cap, &ci->vfs_inode);
>> >
>> > + mdsc = ceph_inode_to_client(&ci->vfs_inode)->mdsc;
>> > +
>> > /* remove from inode's cap rbtree, and clear auth cap */
>> > rb_erase(&cap->ci_node, &ci->i_caps);
>> > if (ci->i_auth_cap == cap) {
>
> --
> Jeff Layton <jlayton@kernel.org>
>
prev parent reply other threads:[~2020-11-12 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 10:45 [PATCH] ceph: fix race in concurrent __ceph_remove_cap invocations Luis Henriques
2020-11-12 12:21 ` Jeff Layton
2020-11-12 12:43 ` Yan, Zheng
2020-11-12 13:22 ` Jeff Layton
2020-11-12 14:45 ` Luis Henriques [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=87lff6d475.fsf@suse.de \
--to=lhenriques@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ukernel@gmail.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