From: syzbot <syzbot+9eb4c69fd4d4a1934f3a@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] kernel BUG in bch2_btree_repair_topology_recurse
Date: Fri, 01 Aug 2025 04:19:03 -0700 [thread overview]
Message-ID: <688ca2a7.a00a0220.26d0e1.006a.GAE@google.com> (raw)
In-Reply-To: <688b3341.a00a0220.26d0e1.003b.GAE@google.com>
syzbot has bisected this issue to:
commit c366b1672d74cb008974f6e36e34dc191621f3bb
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sat Apr 26 13:31:23 2025 +0000
bcachefs: btree_node_data_missing is now autofix
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12b59834580000
start commit: e8d780dcd957 Merge tag 'slab-for-6.17' of git://git.kernel..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11b59834580000
console output: https://syzkaller.appspot.com/x/log.txt?x=16b59834580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b45b5c69b7ae37ec
dashboard link: https://syzkaller.appspot.com/bug?extid=9eb4c69fd4d4a1934f3a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16d2c834580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11d32cf0580000
Reported-by: syzbot+9eb4c69fd4d4a1934f3a@syzkaller.appspotmail.com
Fixes: c366b1672d74 ("bcachefs: btree_node_data_missing is now autofix")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-08-01 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 9:11 [syzbot] [bcachefs?] kernel BUG in bch2_btree_repair_topology_recurse syzbot
2025-08-01 11:19 ` syzbot [this message]
2025-08-01 23:03 ` 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=688ca2a7.a00a0220.26d0e1.006a.GAE@google.com \
--to=syzbot+9eb4c69fd4d4a1934f3a@syzkaller.appspotmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.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