All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8deb6ff4415db67a9f18@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
	 linux-kernel@vger.kernel.org, mmpgouride@gmail.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] kernel BUG in __btree_trans_update_by_path
Date: Sat, 05 Jul 2025 16:32:02 -0700	[thread overview]
Message-ID: <6869b5f2.a00a0220.c7b3.0050.GAE@google.com> (raw)
In-Reply-To: <686611ef.a70a0220.5d25f.0833.GAE@google.com>

syzbot has bisected this issue to:

commit 0803fa689bb9eb8d01867808b886a26e76ff1690
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date:   Thu Jun 26 23:52:42 2025 +0000

    bcachefs: -o fix_errors may now be used without -o fsck

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=161ca582580000
start commit:   50c8770a42fa Add linux-next specific files for 20250702
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=151ca582580000
console output: https://syzkaller.appspot.com/x/log.txt?x=111ca582580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d831c9dfe03f77ec
dashboard link: https://syzkaller.appspot.com/bug?extid=8deb6ff4415db67a9f18
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1311d3d4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1770f982580000

Reported-by: syzbot+8deb6ff4415db67a9f18@syzkaller.appspotmail.com
Fixes: 0803fa689bb9 ("bcachefs: -o fix_errors may now be used without -o fsck")

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

      parent reply	other threads:[~2025-07-05 23:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03  5:15 [syzbot] [bcachefs?] kernel BUG in __btree_trans_update_by_path syzbot
2025-07-03  7:19 ` Alan Huang
2025-07-05 23:32 ` 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=6869b5f2.a00a0220.c7b3.0050.GAE@google.com \
    --to=syzbot+8deb6ff4415db67a9f18@syzkaller.appspotmail.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmpgouride@gmail.com \
    --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.