[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000000000000a4f241061659def0@google.com>
Date: Thu, 18 Apr 2024 00:25:03 -0700
From: syzbot <syzbot+9157524e62303fd7b21c@...kaller.appspotmail.com>
To: axboe@...nel.dk, brauner@...nel.org, jack@...e.cz,
jfs-discussion@...ts.sourceforge.net, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, shaggy@...nel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [jfs?] INFO: task hung in jfs_commit_inode (2)
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=155eb8f7180000
start commit: 4f9e7fabf864 Merge tag 'trace-v6.5-rc6' of git://git.kerne..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1b32f62c755c3a9c
dashboard link: https://syzkaller.appspot.com/bug?extid=9157524e62303fd7b21c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101aff5ba80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d78db0680000
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