From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: 000000000000219dcd05e9f95ed9@google.com
Cc: linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
syzbot <syzbot+b8c672b0e22615c80fe0@syzkaller.appspotmail.com>
Subject: Re: [syzbot] KASAN: use-after-free Read in nilfs_segctor_confirm
Date: Mon, 3 Oct 2022 00:52:18 +0900 [thread overview]
Message-ID: <CAKFNMom7Z_5QWaGTG-=C67n0aT__nu4Wfs=Tsa3jgpXQMtWkEA@mail.gmail.com> (raw)
In-Reply-To: <3b7a3398-0826-04de-f805-c926b39e7d35@gmail.com>
On Sun, Oct 2, 2022 at 6:25 PM Khalid Masum wrote:
>
> Hi all,
>
> The reproducer triggers the same bug in upstream 6.0-rc7 as well.
>
>
> Thanks,
>
> -- Khalid Masum
It looks like this and a few similar issues are caused by duplicate
inode allocation with the same inode number
as the root inode on a corrupted disk image.
I'm now digging into the issue and trying to fix it.
Thanks,
Ryusuke Konishi
WARNING: multiple messages have this Message-ID (diff)
From: Ryusuke Konishi <konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: 000000000000219dcd05e9f95ed9-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
syzbot
<syzbot+b8c672b0e22615c80fe0-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
Subject: Re: [syzbot] KASAN: use-after-free Read in nilfs_segctor_confirm
Date: Mon, 3 Oct 2022 00:52:18 +0900 [thread overview]
Message-ID: <CAKFNMom7Z_5QWaGTG-=C67n0aT__nu4Wfs=Tsa3jgpXQMtWkEA@mail.gmail.com> (raw)
In-Reply-To: <3b7a3398-0826-04de-f805-c926b39e7d35-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Sun, Oct 2, 2022 at 6:25 PM Khalid Masum wrote:
>
> Hi all,
>
> The reproducer triggers the same bug in upstream 6.0-rc7 as well.
>
>
> Thanks,
>
> -- Khalid Masum
It looks like this and a few similar issues are caused by duplicate
inode allocation with the same inode number
as the root inode on a corrupted disk image.
I'm now digging into the issue and trying to fix it.
Thanks,
Ryusuke Konishi
next prev parent reply other threads:[~2022-10-02 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 9:25 [syzbot] KASAN: use-after-free Read in nilfs_segctor_confirm Khalid Masum
2022-10-02 9:25 ` Khalid Masum
2022-10-02 15:52 ` Ryusuke Konishi [this message]
2022-10-02 15:52 ` Ryusuke Konishi
-- strict thread matches above, loose matches on Subject: below --
2022-10-01 13:48 syzbot
2022-10-01 13:48 ` syzbot
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='CAKFNMom7Z_5QWaGTG-=C67n0aT__nu4Wfs=Tsa3jgpXQMtWkEA@mail.gmail.com' \
--to=konishi.ryusuke@gmail.com \
--cc=000000000000219dcd05e9f95ed9@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=syzbot+b8c672b0e22615c80fe0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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.