public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a6af6dbf934175da5161@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_bkey_pack_pos_lossy (2)
Date: Sat, 12 Jul 2025 01:11:03 -0700	[thread overview]
Message-ID: <68721897.a00a0220.26a83e.0073.GAE@google.com> (raw)
In-Reply-To: <683dad17.a00a0220.d8eae.0054.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 263561649ee5875a922f4358e96d3deb17a91021
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date:   Sat Jun 7 18:27:35 2025 +0000

    bcachefs: Don't persistently run scan_for_btree_nodes

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=141eae8c580000
start commit:   90b83efa6701 Merge tag 'bpf-next-6.16' of git://git.kernel..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=ae6d9a7dd3ac8772
dashboard link: https://syzkaller.appspot.com/bug?extid=a6af6dbf934175da5161
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=159907f4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1758a482580000

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

#syz fix: bcachefs: Don't persistently run scan_for_btree_nodes

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

      reply	other threads:[~2025-07-12  8:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 13:54 [syzbot] [bcachefs?] kernel BUG in bch2_bkey_pack_pos_lossy (2) syzbot
2025-07-12  8:11 ` 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=68721897.a00a0220.26a83e.0073.GAE@google.com \
    --to=syzbot+a6af6dbf934175da5161@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