From: syzbot <syzbot+727c886b67040701c448@syzkaller.appspotmail.com>
To: dakr@kernel.org, gregkh@linuxfoundation.org,
kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, rafael@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs] WARNING: locking bug in simple_recursive_removal
Date: Sun, 23 Feb 2025 00:16:01 -0800 [thread overview]
Message-ID: <67bad941.050a0220.bbfd1.0011.GAE@google.com> (raw)
In-Reply-To: <67b44ef3.050a0220.173698.004c.GAE@google.com>
syzbot has bisected this issue to:
commit 14152654805256d760315ec24e414363bfa19a06
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Mon Nov 25 05:21:27 2024 +0000
bcachefs: Bad btree roots are now autofix
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14dffae4580000
start commit: 2408a807bfc3 Merge tag 'vfs-6.14-rc4.fixes' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16dffae4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=12dffae4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6cc40dfe827ffb85
dashboard link: https://syzkaller.appspot.com/bug?extid=727c886b67040701c448
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17982498580000
Reported-by: syzbot+727c886b67040701c448@syzkaller.appspotmail.com
Fixes: 141526548052 ("bcachefs: Bad btree roots are now autofix")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-02-23 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 9:12 [syzbot] [bcachefs] WARNING: locking bug in simple_recursive_removal syzbot
2025-02-18 15:32 ` syzbot
2025-02-23 8:16 ` syzbot [this message]
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=67bad941.050a0220.bbfd1.0011.GAE@google.com \
--to=syzbot+727c886b67040701c448@syzkaller.appspotmail.com \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox