From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+693985588d7a5e439483@syzkaller.appspotmail.com>
Cc: adilger.kernel@dilger.ca, axboe@kernel.dk, brauner@kernel.org,
jack@suse.cz, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, nathan@kernel.org, ndesaulniers@google.com,
syzkaller-bugs@googlegroups.com, trix@redhat.com, tytso@mit.edu
Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_enable_quotas
Date: Mon, 12 Feb 2024 14:23:50 +0100 [thread overview]
Message-ID: <20240212132350.ipdht3ttxyivl33p@quack3> (raw)
In-Reply-To: <0000000000002903a406110849e9@google.com>
On Sat 10-02-24 06:59:05, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 6f861765464f43a71462d52026fbddfc858239a5
> Author: Jan Kara <jack@suse.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@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2024-02-12 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 18:25 [syzbot] [ext4?] kernel BUG in ext4_enable_quotas syzbot
2023-08-23 18:08 ` syzbot
2024-02-10 14:59 ` syzbot
2024-02-12 13:23 ` Jan Kara [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=20240212132350.ipdht3ttxyivl33p@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=syzbot+693985588d7a5e439483@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.com \
--cc=tytso@mit.edu \
/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