From: Xiubo Li <xiubli@redhat.com>
To: "Luís Henriques" <lhenriques@suse.de>
Cc: ceph-devel@vger.kernel.org, jlayton@kernel.org,
mchangir@redhat.com, idryomov@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH] ceph: avoid putting the realm twice when docoding snaps fails
Date: Mon, 7 Nov 2022 18:58:08 +0800 [thread overview]
Message-ID: <b9366f31-01b6-a5f7-ea11-5e0f88934f58@redhat.com> (raw)
In-Reply-To: <Y2jgZ52dV+TzWhlQ@suse.de>
On 07/11/2022 18:39, Luís Henriques wrote:
> On Mon, Nov 07, 2022 at 03:17:59PM +0800, 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 | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/ceph/snap.c b/fs/ceph/snap.c
>> index 9bceed2ebda3..baf17df05107 100644
>> --- a/fs/ceph/snap.c
>> +++ b/fs/ceph/snap.c
>> @@ -849,10 +849,12 @@ int ceph_update_snap_trace(struct ceph_mds_client *mdsc,
>> if (realm_to_rebuild && p >= e)
>> rebuild_snap_realms(realm_to_rebuild, &dirty_realms);
>>
>> - if (!first_realm)
>> + if (!first_realm) {
>> first_realm = realm;
>> - else
>> + realm = NULL;
>> + } else {
>> ceph_put_snap_realm(mdsc, realm);
>> + }
>>
>> if (p < e)
>> goto more;
>> --
>> 2.31.1
>>
> This patch looks correct to me. But I wonder if there's a deeper problem
> there (probably not on the kernel client). Because the other question is:
> why are we failing to decode the snaps? But I guess this fix is worth it
> anyway.
Yeah, good question.
At the same time the MDS also crashed [1][2] just before the kernel
crash was triggered seconds later. And the metadata in cephfs was
corrupted due to some reasons.
[1] https://tracker.ceph.com/issues/56140
[2] https://tracker.ceph.com/issues/54546
Thanks!
- Xiubo
> Reviewed-by: Luís Henriques <lhenriques@suse.de>
>
>
> Cheers,
> --
> Luís
>
next prev parent reply other threads:[~2022-11-07 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 7:17 [PATCH] ceph: avoid putting the realm twice when docoding snaps fails xiubli
2022-11-07 10:39 ` Luís Henriques
2022-11-07 10:58 ` Xiubo Li [this message]
2022-11-07 15:21 ` Ilya Dryomov
2022-11-08 2:24 ` Xiubo Li
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=b9366f31-01b6-a5f7-ea11-5e0f88934f58@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 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.