All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+5824b2660896028cfe7f@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?] kernel BUG in bch2_btree_path_level_init (3)
Date: Mon, 23 Dec 2024 20:33:02 -0800	[thread overview]
Message-ID: <676a397e.050a0220.226966.004e.GAE@google.com> (raw)
In-Reply-To: <6766dfca.050a0220.25abdd.0130.GAE@google.com>

syzbot has bisected this issue to:

commit 2d02bfb01b2743da06748ba396ff7da4425488ef
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date:   Fri Jan 5 19:17:57 2024 +0000

    bcachefs: improve validate_bset_keys()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11ffd4c4580000
start commit:   4bbf9020becb Linux 6.13-rc4
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=13ffd4c4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=15ffd4c4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4c4096b0d467a682
dashboard link: https://syzkaller.appspot.com/bug?extid=5824b2660896028cfe7f
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16d5dfe8580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=179d8adf980000

Reported-by: syzbot+5824b2660896028cfe7f@syzkaller.appspotmail.com
Fixes: 2d02bfb01b27 ("bcachefs: improve validate_bset_keys()")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2024-12-24  4:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-21 15:33 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_level_init (3) syzbot
2024-12-24  4:33 ` syzbot [this message]
2025-07-19  1:31 ` 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=676a397e.050a0220.226966.004e.GAE@google.com \
    --to=syzbot+5824b2660896028cfe7f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.