[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000000000000cf2d2d06127def32@google.com>
Date: Wed, 28 Feb 2024 20:46:03 -0800
From: syzbot <syzbot+092b28923eb79e0f3c41@...kaller.appspotmail.com>
To: agruenba@...hat.com, axboe@...nel.dk, brauner@...nel.org,
cluster-devel@...hat.com, gfs2@...ts.linux.dev, jack@...e.cz,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
rpeterso@...hat.com, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [gfs2?] WARNING in gfs2_check_blk_type
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=108aa9ba180000
start commit: 861deac3b092 Linux 6.7-rc7
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=10c7857ed774dc3e
dashboard link: https://syzkaller.appspot.com/bug?extid=092b28923eb79e0f3c41
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1440171ae80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11b1205ee80000
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
Powered by blists - more mailing lists