All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+bd56952613b5dae47ca4@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_evacuate_bucket
Date: Mon, 25 Nov 2024 22:18:03 -0800	[thread overview]
Message-ID: <6745681b.050a0220.1286eb.0010.GAE@google.com> (raw)
In-Reply-To: <67447614.050a0220.1cc393.007f.GAE@google.com>

syzbot has bisected this issue to:

commit 33dfafa90285c0873a24d633877d505ab8e3fc20
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date:   Wed Jun 19 13:55:48 2024 +0000

    bcachefs: Fix safe errors by default

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=117715c0580000
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=137715c0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=157715c0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e92fc420ca55fe33
dashboard link: https://syzkaller.appspot.com/bug?extid=bd56952613b5dae47ca4
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=124c25c0580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=164c25c0580000

Reported-by: syzbot+bd56952613b5dae47ca4@syzkaller.appspotmail.com
Fixes: 33dfafa90285 ("bcachefs: Fix safe errors by default")

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

  reply	other threads:[~2024-11-26  6:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 13:05 [syzbot] [bcachefs?] kernel BUG in bch2_evacuate_bucket syzbot
2024-11-26  6:18 ` syzbot [this message]
2024-11-29  0:39 ` [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=6745681b.050a0220.1286eb.0010.GAE@google.com \
    --to=syzbot+bd56952613b5dae47ca4@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.