All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+08d08d52c3a09bfc70f7@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?] WARNING in bch2_fs_release
Date: Sun, 09 Feb 2025 11:27:01 -0800	[thread overview]
Message-ID: <67a90185.050a0220.3d72c.0040.GAE@google.com> (raw)
In-Reply-To: <66f01abe.050a0220.3195df.009d.GAE@google.com>

syzbot has bisected this issue to:

commit 8b22abb4c84058e9533d71a4814e54316ba2621f
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date:   Sat Oct 12 02:53:09 2024 +0000

    bcachefs: -o norecovery now bails out of recovery earlier

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=121ddb18580000
start commit:   8f6629c004b1 kbuild: Move -Wenum-enum-conversion to W=2
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=111ddb18580000
console output: https://syzkaller.appspot.com/x/log.txt?x=161ddb18580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=147b7d49d83b8036
dashboard link: https://syzkaller.appspot.com/bug?extid=08d08d52c3a09bfc70f7
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1312cbdf980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=129411b0580000

Reported-by: syzbot+08d08d52c3a09bfc70f7@syzkaller.appspotmail.com
Fixes: 8b22abb4c840 ("bcachefs: -o norecovery now bails out of recovery earlier")

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

  parent reply	other threads:[~2025-02-09 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-22 13:25 [syzbot] [bcachefs?] WARNING in bch2_fs_release syzbot
2025-02-09  0:19 ` syzbot
2025-02-09 19:27 ` syzbot [this message]
2025-05-09 11:46 ` 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=67a90185.050a0220.3d72c.0040.GAE@google.com \
    --to=syzbot+08d08d52c3a09bfc70f7@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 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.