mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+64e6509c7f777aec3a24@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_get_scanned_nodes
Date: Thu, 28 Nov 2024 08:47:02 -0800	[thread overview]
Message-ID: <67489e86.050a0220.253251.008a.GAE@google.com> (raw)
In-Reply-To: <67483ca4.050a0220.253251.007d.GAE@google.com>

syzbot has bisected this issue to:

commit 50eecc37ec7c9caab87c938b912bb5c686316ea5
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date:   Wed Nov 27 05:29:52 2024 +0000

    bcachefs: struct bkey_validate_context

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=10a64f78580000
start commit:   f486c8aa16b8 Add linux-next specific files for 20241128
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=12a64f78580000
console output: https://syzkaller.appspot.com/x/log.txt?x=14a64f78580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e348a4873516af92
dashboard link: https://syzkaller.appspot.com/bug?extid=64e6509c7f777aec3a24
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1389ef5f980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=164a8f78580000

Reported-by: syzbot+64e6509c7f777aec3a24@syzkaller.appspotmail.com
Fixes: 50eecc37ec7c ("bcachefs: struct bkey_validate_context")

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

  reply	other threads:[~2024-11-28 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28  9:49 syzbot
2024-11-28 16:47 ` syzbot [this message]
2024-11-28 20:31 ` [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=67489e86.050a0220.253251.008a.GAE@google.com \
    --to=syzbot+64e6509c7f777aec3a24@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
Powered by JetHome