public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6279b273d888c2017726@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hch@lst.de, linux-block@vger.kernel.org,
	 linux-kernel@vger.kernel.org, ming.lei@redhat.com,
	netdev@vger.kernel.org,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] possible deadlock in blk_mq_update_nr_hw_queues
Date: Sun, 13 Jul 2025 05:20:03 -0700	[thread overview]
Message-ID: <6873a473.a70a0220.3b380f.0031.GAE@google.com> (raw)
In-Reply-To: <6743b30d.050a0220.1cc393.004e.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=14ea5d82580000
start commit:   a52f9f0d77f2 Merge tag 'batadv-next-pullrequest-20250710' ..
git tree:       net-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=16ea5d82580000
console output: https://syzkaller.appspot.com/x/log.txt?x=12ea5d82580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f8235fb7e74dd7f6
dashboard link: https://syzkaller.appspot.com/bug?extid=6279b273d888c2017726
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14321d82580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=179590f0580000

Reported-by: syzbot+6279b273d888c2017726@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:[~2025-07-13 12:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-24 23:13 [syzbot] [block?] possible deadlock in blk_mq_update_nr_hw_queues syzbot
2025-04-03 19:36 ` syzbot
2025-07-13 12:20 ` 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=6873a473.a70a0220.3b380f.0031.GAE@google.com \
    --to=syzbot+6279b273d888c2017726@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=netdev@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