From: syzbot <syzbot+7836a68852a10ec3d790@syzkaller.appspotmail.com>
To: amir73il@gmail.com, kent.overstreet@linux.dev,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
mmpgouride@gmail.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [bcachefs?] possible deadlock in bch2_symlink
Date: Mon, 18 Aug 2025 03:41:03 -0700 [thread overview]
Message-ID: <68a3033f.050a0220.e29e5.00a0.GAE@google.com> (raw)
In-Reply-To: <CAOQ4uxiPPb70mx0Pr4Ph6hw2j63Q8=PZaxBx3N0KP=d7Ko=1KQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+7836a68852a10ec3d790@syzkaller.appspotmail.com
Tested-by: syzbot+7836a68852a10ec3d790@syzkaller.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.
next prev parent reply other threads:[~2025-08-18 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 7:31 [syzbot] [bcachefs?] possible deadlock in bch2_symlink syzbot
2025-02-08 9:14 ` syzbot
2025-08-04 3:02 ` Alan Huang
2025-08-04 3:23 ` Al Viro
2025-08-04 3:27 ` Kent Overstreet
2025-08-18 9:19 ` Amir Goldstein
2025-08-18 10:41 ` syzbot [this message]
2025-08-04 23:12 ` Forwarded: syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68a3033f.050a0220.e29e5.00a0.GAE@google.com \
--to=syzbot+7836a68852a10ec3d790@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mmpgouride@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.