From: syzbot <syzbot+3ba6dd3d414ec2296f3c@syzkaller.appspotmail.com>
To: anna.luese@v-bien.de, 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_node_iter_init (2)
Date: Thu, 10 Jul 2025 09:40:03 -0700 [thread overview]
Message-ID: <686fece3.a00a0220.26a83e.0018.GAE@google.com> (raw)
In-Reply-To: <686ea916.050a0220.385921.0013.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=128dda8c580000
start commit: 733923397fd9 Merge tag 'pwm/for-6.16-rc6-fixes' of git://g..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=118dda8c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=168dda8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bd2783a0a99d4ed0
dashboard link: https://syzkaller.appspot.com/bug?extid=3ba6dd3d414ec2296f3c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12101bd4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12609a8c580000
Reported-by: syzbot+3ba6dd3d414ec2296f3c@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-07-10 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 17:38 [syzbot] [bcachefs?] kernel BUG in bch2_btree_node_iter_init (2) syzbot
2025-07-10 16:40 ` syzbot [this message]
2025-07-19 1:55 ` Kent Overstreet
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=686fece3.a00a0220.26a83e.0018.GAE@google.com \
--to=syzbot+3ba6dd3d414ec2296f3c@syzkaller.appspotmail.com \
--cc=anna.luese@v-bien.de \
--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