linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+96f61f1ad84e33cee93e@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, hch@lst.de, jack@suse.cz,
	 linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] WARNING in bdev_file_open_by_dev
Date: Sat, 10 Feb 2024 07:32:03 -0800	[thread overview]
Message-ID: <0000000000001493e2061108bfd4@google.com> (raw)
In-Reply-To: <0000000000008ca4ed0610f6d017@google.com>

syzbot has bisected this issue to:

commit e6d7c6cd8e6aeb8b4add207d31dff240680ff573
Author: Christian Brauner <brauner@kernel.org>
Date:   Tue Jan 23 13:26:20 2024 +0000

    block/genhd: port disk_scan_partitions() to file

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15805cec180000
start commit:   445a555e0623 Add linux-next specific files for 20240209
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=17805cec180000
console output: https://syzkaller.appspot.com/x/log.txt?x=13805cec180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=85aa3388229f9ea9
dashboard link: https://syzkaller.appspot.com/bug?extid=96f61f1ad84e33cee93e
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=178b1e20180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=143db9f4180000

Reported-by: syzbot+96f61f1ad84e33cee93e@syzkaller.appspotmail.com
Fixes: e6d7c6cd8e6a ("block/genhd: port disk_scan_partitions() to file")

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

      parent reply	other threads:[~2024-02-10 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 18:08 [syzbot] [block?] WARNING in bdev_file_open_by_dev syzbot
2024-02-09 22:34 ` Christian Brauner
2024-02-09 22:35 ` Christian Brauner
2024-02-10  0:17   ` syzbot
2024-02-10  8:52     ` Christian Brauner
2024-02-10  9:23       ` syzbot
2024-02-10 15: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=0000000000001493e2061108bfd4@google.com \
    --to=syzbot+96f61f1ad84e33cee93e@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).