All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+210dfbddd64294066983@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_trans_update_by_path
Date: Mon, 07 Jul 2025 05:00:06 -0700	[thread overview]
Message-ID: <686bb6c6.a00a0220.c7b3.0084.GAE@google.com> (raw)
In-Reply-To: <6853f202.a00a0220.137b3.0005.GAE@google.com>

syzbot has bisected this issue to:

commit d21262d4e35d448cbc80092c91f04cc0a5f2b0b4
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date:   Wed May 28 18:26:33 2025 +0000

    bcachefs: bch2_dev_journal_bucket_delete()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=100a928c580000
start commit:   d7b8f8e20813 Linux 6.16-rc5
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=120a928c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=140a928c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=72aa0474e3c3b9ac
dashboard link: https://syzkaller.appspot.com/bug?extid=210dfbddd64294066983
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=141a1f70580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=121a1f70580000

Reported-by: syzbot+210dfbddd64294066983@syzkaller.appspotmail.com
Fixes: d21262d4e35d ("bcachefs: bch2_dev_journal_bucket_delete()")

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

  parent reply	other threads:[~2025-07-07 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 11:18 [syzbot] [bcachefs?] kernel BUG in bch2_trans_update_by_path syzbot
2025-07-06 22:48 ` syzbot
2025-07-07 12:00 ` syzbot [this message]
2025-08-05  3:52 ` Alan Huang

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=686bb6c6.a00a0220.c7b3.0084.GAE@google.com \
    --to=syzbot+210dfbddd64294066983@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.