mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+7c8101d4d0ba2eb511d7@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?] divide error in bch2_sb_members_v2_to_text
Date: Tue, 10 Jun 2025 23:47:01 -0700	[thread overview]
Message-ID: <68492665.050a0220.33aa0e.0366.GAE@google.com> (raw)
In-Reply-To: <68488453.a70a0220.27c366.0068.GAE@google.com>

syzbot has bisected this issue to:

commit c5ae261c8095a37174e17eb13c5485cbd1b3bb20
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date:   Sun Jun 8 15:31:23 2025 +0000

    bcachefs: Don't trust sb->nr_devices in members_to_text()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=10c319d4580000
start commit:   b27cc623e01b Add linux-next specific files for 20250610
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=12c319d4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=14c319d4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=846e731334efc0f8
dashboard link: https://syzkaller.appspot.com/bug?extid=7c8101d4d0ba2eb511d7
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=175a260c580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1129e9d4580000

Reported-by: syzbot+7c8101d4d0ba2eb511d7@syzkaller.appspotmail.com
Fixes: c5ae261c8095 ("bcachefs: Don't trust sb->nr_devices in members_to_text()")

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

  parent reply	other threads:[~2025-06-11  6:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 19:15 syzbot
2025-06-10 19:36 ` syzbot
2025-06-11  6:47 ` syzbot [this message]
2025-06-19 21:00 ` [syzbot] 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=68492665.050a0220.33aa0e.0366.GAE@google.com \
    --to=syzbot+7c8101d4d0ba2eb511d7@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
Powered by JetHome