[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0000000000000c6e0a0612e6bd58@google.com>
Date: Tue, 05 Mar 2024 01:48:03 -0800
From: syzbot <syzbot+577d06779fa95206ba66@...kaller.appspotmail.com>
To: agruenba@...hat.com, axboe@...nel.dk, brauner@...nel.org,
gfs2@...ts.linux.dev, jack@...e.cz, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, rpeterso@...hat.com,
syzkaller-bugs@...glegroups.com, yuran.pereira@...mail.com
Subject: Re: [syzbot] [gfs2?] BUG: sleeping function called from invalid
context in gfs2_withdraw
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=119f927a180000
start commit: 6465e260f487 Linux 6.6-rc3
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8d7d7928f78936aa
dashboard link: https://syzkaller.appspot.com/bug?extid=577d06779fa95206ba66
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10dbcdc1680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17a367b6680000
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