public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+c7aacacf99dcfd3475a7@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?] INFO: task hung in bch2_fs_read_only
Date: Tue, 08 Apr 2025 01:41:02 -0700	[thread overview]
Message-ID: <67f4e11e.050a0220.396535.055a.GAE@google.com> (raw)
In-Reply-To: <66f53709.050a0220.211276.0068.GAE@google.com>

syzbot suspects this issue was fixed by commit:

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=106bd23f980000
start commit:   aa486552a110 Merge tag 'memblock-v6.12-rc1' of git://git.k..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=bad8b2899350fd0b
dashboard link: https://syzkaller.appspot.com/bug?extid=c7aacacf99dcfd3475a7
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=102b699f980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=151ccaa9980000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: bcachefs: -o norecovery now bails out of recovery earlier

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

      reply	other threads:[~2025-04-08  8:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 10:27 [syzbot] [bcachefs?] INFO: task hung in bch2_fs_read_only syzbot
2025-04-08  8:41 ` syzbot [this message]

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=67f4e11e.050a0220.396535.055a.GAE@google.com \
    --to=syzbot+c7aacacf99dcfd3475a7@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