[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKFNMom7Z_5QWaGTG-=C67n0aT__nu4Wfs=Tsa3jgpXQMtWkEA@mail.gmail.com>
Date: Mon, 3 Oct 2022 00:52:18 +0900
From: Ryusuke Konishi <konishi.ryusuke@...il.com>
To: 000000000000219dcd05e9f95ed9@...gle.com
Cc: linux-kernel@...r.kernel.org, linux-nilfs@...r.kernel.org,
syzkaller-bugs@...glegroups.com,
syzbot <syzbot+b8c672b0e22615c80fe0@...kaller.appspotmail.com>
Subject: Re: [syzbot] KASAN: use-after-free Read in nilfs_segctor_confirm
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
Powered by blists - more mailing lists