[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240212132350.ipdht3ttxyivl33p@quack3>
Date: Mon, 12 Feb 2024 14:23:50 +0100
From: Jan Kara <jack@...e.cz>
To: syzbot <syzbot+693985588d7a5e439483@...kaller.appspotmail.com>
Cc: adilger.kernel@...ger.ca, axboe@...nel.dk, brauner@...nel.org,
jack@...e.cz, linux-ext4@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev, nathan@...nel.org, ndesaulniers@...gle.com,
syzkaller-bugs@...glegroups.com, trix@...hat.com, tytso@....edu
Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_enable_quotas
On Sat 10-02-24 06:59:05, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 6f861765464f43a71462d52026fbddfc858239a5
> Author: Jan Kara <jack@...e.cz>
> Date: Wed Nov 1 17:43:10 2023 +0000
>
> fs: Block writes to mounted block devices
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=147e5b20180000
> start commit: 89bf6209cad6 Merge tag 'devicetree-fixes-for-6.5-2' of git..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=1b32f62c755c3a9c
> dashboard link: https://syzkaller.appspot.com/bug?extid=693985588d7a5e439483
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11ba1fefa80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1636640fa80000
>
> If the result looks correct, please mark the issue as fixed by replying with:
The syzbot reproducer seems to mess with multiple ext4 mounts stacked on
one another and the loop device as well. Quite likely it managed to corrupt
the mounted filesystem. So:
#syz fix: fs: Block writes to mounted block devices
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists