All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+ca7d7c797fee31d2b474@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hch@lst.de, linux-block@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	ming.lei@redhat.com,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] [block?] possible deadlock in blk_mq_alloc_request
Date: Tue, 24 Dec 2024 04:54:03 -0800	[thread overview]
Message-ID: <676aaeeb.050a0220.2f3838.01aa.GAE@google.com> (raw)
In-Reply-To: <672ad716.050a0220.2a847.1a9e.GAE@google.com>

syzbot has bisected this issue to:

commit f1be1788a32e8fa63416ad4518bbd1a85a825c9d
Author: Ming Lei <ming.lei@redhat.com>
Date:   Fri Oct 25 00:37:20 2024 +0000

    block: model freeze & enter queue as lock for supporting lockdep

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15fd34c4580000
start commit:   c88416ba074a Add linux-next specific files for 20241101
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=17fd34c4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=13fd34c4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=704b6be2ac2f205f
dashboard link: https://syzkaller.appspot.com/bug?extid=ca7d7c797fee31d2b474
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1250b630580000

Reported-by: syzbot+ca7d7c797fee31d2b474@syzkaller.appspotmail.com
Fixes: f1be1788a32e ("block: model freeze & enter queue as lock for supporting lockdep")

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

      parent reply	other threads:[~2024-12-24 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  2:40 [syzbot] [block?] possible deadlock in blk_mq_alloc_request syzbot
2024-11-06  3:48 ` Ming Lei
2024-11-06  4:18   ` syzbot
2024-12-24 12:54 ` 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=676aaeeb.050a0220.2f3838.01aa.GAE@google.com \
    --to=syzbot+ca7d7c797fee31d2b474@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ming.lei@redhat.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.