From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+2c4a3b922a860084cc7f@syzkaller.appspotmail.com>
Cc: adilger.kernel@dilger.ca, axboe@kernel.dk, brauner@kernel.org,
eadavis@qq.com, jack@suse.cz, libaokun1@huawei.com,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, viro@zeniv.linux.org.uk, willy@infradead.org,
yangerkun@huawei.com
Subject: Re: [syzbot] [ext4?] WARNING in lock_two_nondirectories
Date: Mon, 12 Feb 2024 14:28:52 +0100 [thread overview]
Message-ID: <20240212132852.5fxliee4izjkx74w@quack3> (raw)
In-Reply-To: <000000000000b9df7e061123f594@google.com>
On Sun 11-02-24 16:00:04, 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=15477434180000
> start commit: a39b6ac3781d Linux 6.7-rc5
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=e043d554f0a5f852
> dashboard link: https://syzkaller.appspot.com/bug?extid=2c4a3b922a860084cc7f
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1687292ee80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d8adbce80000
>
> If the result looks correct, please mark the issue as fixed by replying with:
Another repro that seems to be corrupting the fs metadata:
#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:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 13:49 [syzbot] [ext4?] WARNING in lock_two_nondirectories syzbot
2023-12-24 11:53 ` [PATCH] ext4: fix " Edward Adam Davis
2023-12-24 14:13 ` Matthew Wilcox
2023-12-25 1:38 ` Baokun Li
2023-12-25 2:07 ` Al Viro
2023-12-25 2:33 ` Baokun Li
2023-12-25 2:49 ` Theodore Ts'o
2023-12-25 2:56 ` Baokun Li
2023-12-25 2:11 ` Theodore Ts'o
2023-12-25 2:15 ` Al Viro
2023-12-25 2:46 ` Baokun Li
2024-02-12 0:00 ` [syzbot] [ext4?] " syzbot
2024-02-12 13:28 ` 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=20240212132852.5fxliee4izjkx74w@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=eadavis@qq.com \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2c4a3b922a860084cc7f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=yangerkun@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox