From: syzbot <syzbot+2f7c2225ed8a5cb24af1@syzkaller.appspotmail.com>
To: bfoster@redhat.com, kent.overstreet@linux.dev,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] BUG: corrupted list in bch2_btree_and_journal_iter_exit
Date: Wed, 27 Nov 2024 04:53:02 -0800 [thread overview]
Message-ID: <6747162e.050a0220.1286eb.0031.GAE@google.com> (raw)
In-Reply-To: <67447b76.050a0220.1cc393.0086.GAE@google.com>
syzbot has bisected this issue to:
commit d1adfe4e7e4e7ea225547a07c4b79c314c50c6fb
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sun Apr 7 03:26:36 2024 +0000
bcachefs: move root node topo checks to node_check_topology()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17e6e1e8580000
start commit: 9f16d5e6f220 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1416e1e8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1016e1e8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e92fc420ca55fe33
dashboard link: https://syzkaller.appspot.com/bug?extid=2f7c2225ed8a5cb24af1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16cf575f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14be0530580000
Reported-by: syzbot+2f7c2225ed8a5cb24af1@syzkaller.appspotmail.com
Fixes: d1adfe4e7e4e ("bcachefs: move root node topo checks to node_check_topology()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-11-27 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 13:28 [syzbot] [bcachefs?] BUG: corrupted list in bch2_btree_and_journal_iter_exit syzbot
2024-11-27 12:53 ` syzbot [this message]
2024-11-28 20:12 ` [syzbot] 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=6747162e.050a0220.1286eb.0031.GAE@google.com \
--to=syzbot+2f7c2225ed8a5cb24af1@syzkaller.appspotmail.com \
--cc=bfoster@redhat.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