[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <68a3033f.050a0220.e29e5.00a0.GAE@google.com>
Date: Mon, 18 Aug 2025 03:41:03 -0700
From: syzbot <syzbot+7836a68852a10ec3d790@...kaller.appspotmail.com>
To: amir73il@...il.com, kent.overstreet@...ux.dev,
linux-bcachefs@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-unionfs@...r.kernel.org, miklos@...redi.hu, mmpgouride@...il.com,
syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk
Subject: Re: [syzbot] [bcachefs?] possible deadlock in bch2_symlink
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+7836a68852a10ec3d790@...kaller.appspotmail.com
Tested-by: syzbot+7836a68852a10ec3d790@...kaller.appspotmail.com
Tested on:
commit: 9e7e7e36 ovl: use I_MUTEX_PARENT when locking parent i..
git tree: https://github.com/amir73il/linux ovl-fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=11d09ba2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=41498776bd40da1
dashboard link: https://syzkaller.appspot.com/bug?extid=7836a68852a10ec3d790
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
Powered by blists - more mailing lists