From: syzbot <syzbot+9743a41f74f00e50fc77@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, axboe@kernel.dk, brauner@kernel.org,
hch@infradead.org, hch@lst.de, jack@suse.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
liushixin2@huawei.com, nogikh@google.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [udf] WARNING in invalidate_bh_lru
Date: Sat, 02 Mar 2024 04:14:04 -0800 [thread overview]
Message-ID: <000000000000af5c290612ac6d86@google.com> (raw)
In-Reply-To: <000000000000eccdc505f061d47f@google.com>
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=14a093ce180000
start commit: 9a3dad63edbe Merge tag '6.6-rc5-ksmbd-server-fixes' of git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=11e478e28144788c
dashboard link: https://syzkaller.appspot.com/bug?extid=9743a41f74f00e50fc77
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16ebc3c5680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=122e8275680000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs: Block writes to mounted block devices
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-03-02 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 2:57 [syzbot] [sysv?] [vfs?] WARNING in invalidate_bh_lru syzbot
2023-04-30 6:40 ` Theodore Ts'o
2023-04-30 6:40 ` syzbot
2023-04-30 16:12 ` Theodore Ts'o
2023-05-01 9:18 ` Aleksandr Nogikh
2023-05-03 4:31 ` Theodore Ts'o
2023-06-03 17:35 ` [syzbot] [udf] " syzbot
2024-03-02 12:14 ` syzbot [this message]
2024-03-11 9:32 ` Jan Kara
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=000000000000af5c290612ac6d86@google.com \
--to=syzbot+9743a41f74f00e50fc77@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=nogikh@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).