From: syzbot <syzbot+725322cc4ff5c53abfac@syzkaller.appspotmail.com>
To: anna-maria@linutronix.de, axboe@kernel.dk, frederic@kernel.org,
kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] [bcachefs?] possible deadlock in get_partial_node (2)
Date: Mon, 10 Mar 2025 01:16:02 -0700 [thread overview]
Message-ID: <67ce9fc2.050a0220.e1a89.01f2.GAE@google.com> (raw)
In-Reply-To: <67b1f949.050a0220.173698.000c.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=1688a7a8580000
start commit: b7c90e3e717a Merge tag 'x86-urgent-2025-03-08' of git://gi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1588a7a8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1188a7a8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=523d3ff8e053340a
dashboard link: https://syzkaller.appspot.com/bug?extid=725322cc4ff5c53abfac
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137c1fa0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e0fa54580000
Reported-by: syzbot+725322cc4ff5c53abfac@syzkaller.appspotmail.com
Fixes: 141526548052 ("bcachefs: Bad btree roots are now autofix")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2025-03-10 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <67b1f949.050a0220.173698.000c.GAE@google.com>
2025-03-10 8:16 ` syzbot [this message]
2025-04-14 19:22 ` [syzbot] [bcachefs?] possible deadlock in get_partial_node (2) 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=67ce9fc2.050a0220.e1a89.01f2.GAE@google.com \
--to=syzbot+725322cc4ff5c53abfac@syzkaller.appspotmail.com \
--cc=anna-maria@linutronix.de \
--cc=axboe@kernel.dk \
--cc=frederic@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).