From: Xiubo Li <xiubli@redhat.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: ceph-devel@vger.kernel.org, lhenriques@suse.de,
jlayton@kernel.org, mchangir@redhat.com, stable@vger.kernel.org
Subject: Re: [PATCH v3] ceph: avoid putting the realm twice when decoding snaps fails
Date: Wed, 9 Nov 2022 09:09:34 +0800 [thread overview]
Message-ID: <62c7c610-3090-4029-fe5b-37326169d647@redhat.com> (raw)
In-Reply-To: <CAOi1vP-XiSj35RDbc3zkoNvHfwRujAA8_BEFW3C=5fo+rPWfiQ@mail.gmail.com>
On 08/11/2022 23:10, Ilya Dryomov wrote:
> On Tue, Nov 8, 2022 at 2:46 PM <xiubli@redhat.com> wrote:
>> From: Xiubo Li <xiubli@redhat.com>
>>
>> When decoding the snaps fails it maybe leaving the 'first_realm'
>> and 'realm' pointing to the same snaprealm memory. And then it'll
>> put it twice and could cause random use-after-free, BUG_ON, etc
>> issues.
>>
>> Cc: stable@vger.kernel.org
>> URL: https://tracker.ceph.com/issues/57686
>> Signed-off-by: Xiubo Li <xiubli@redhat.com>
>> ---
>> fs/ceph/snap.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/fs/ceph/snap.c b/fs/ceph/snap.c
>> index 9bceed2ebda3..f5b0fa1ff705 100644
>> --- a/fs/ceph/snap.c
>> +++ b/fs/ceph/snap.c
>> @@ -775,6 +775,7 @@ int ceph_update_snap_trace(struct ceph_mds_client *mdsc,
>>
>> dout("%s deletion=%d\n", __func__, deletion);
>> more:
>> + realm = NULL;
> Nit: realm doesn't need to be initialized anymore, I would drop that.
I noticed that. Sure will remove that.
Thanks!
- Xiubo
> Thanks,
>
> Ilya
>
prev parent reply other threads:[~2022-11-09 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 13:46 [PATCH v3] ceph: avoid putting the realm twice when decoding snaps fails xiubli
2022-11-08 13:51 ` Greg KH
2022-11-08 15:10 ` Ilya Dryomov
2022-11-09 1:09 ` 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=62c7c610-3090-4029-fe5b-37326169d647@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=lhenriques@suse.de \
--cc=mchangir@redhat.com \
--cc=stable@vger.kernel.org \
/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