[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <67147e64.050a0220.10f4f4.0025.GAE@google.com>
Date: Sat, 19 Oct 2024 20:52:04 -0700
From: syzbot <syzbot+9ef37ac20608f4836256@...kaller.appspotmail.com>
To: konishi.ryusuke@...il.com, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [nilfs?] possible deadlock in nilfs_dirty_inode (4)
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+9ef37ac20608f4836256@...kaller.appspotmail.com
Tested-by: syzbot+9ef37ac20608f4836256@...kaller.appspotmail.com
Tested on:
commit: 715ca9dd Merge tag 'io_uring-6.12-20241019' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1450825f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=16e543edc81a3008
dashboard link: https://syzkaller.appspot.com/bug?extid=9ef37ac20608f4836256
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=148e0c87980000
Note: testing is done by a robot and is best-effort only.
Powered by blists - more mailing lists