From: Ming Lei <ming.lei@redhat.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
linux-block@vger.kernel.org
Subject: Re: Blockdev 6.13-rc lockdep splat regressions
Date: Mon, 13 Jan 2025 17:28:28 +0800 [thread overview]
Message-ID: <Z4TcvNCBXcLJV3vs@fedora> (raw)
In-Reply-To: <ead7c5ce5138912c1f3179d62370b84a64014a38.camel@linux.intel.com>
On Sun, Jan 12, 2025 at 12:33:13PM +0100, Thomas Hellström wrote:
> On Sat, 2025-01-11 at 11:05 +0800, Ming Lei wrote:
> > On Fri, Jan 10, 2025 at 03:36:44PM +0100, Thomas Hellström wrote:
> > > On Fri, 2025-01-10 at 20:13 +0800, Ming Lei wrote:
> > > > On Fri, Jan 10, 2025 at 11:12:58AM +0100, Thomas Hellström wrote:
> > > > > Ming, Others
> > > > >
>
> #2:
> [ 5.595482] ======================================================
> [ 5.596353] WARNING: possible circular locking dependency detected
> [ 5.597231] 6.13.0-rc6+ #122 Tainted: G U
> [ 5.598182] ------------------------------------------------------
> [ 5.599149] (udev-worker)/867 is trying to acquire lock:
> [ 5.600075] ffff9211c02f7948 (&root->kernfs_rwsem){++++}-{4:4}, at:
> kernfs_remove+0x31/0x50
> [ 5.600987]
> but task is already holding lock:
> [ 5.603025] ffff9211e86f41a0 (&q->q_usage_counter(io)#3){++++}-
> {0:0}, at: blk_mq_freeze_queue+0x12/0x20
> [ 5.603033]
> which lock already depends on the new lock.
>
> [ 5.603034]
> the existing dependency chain (in reverse order) is:
> [ 5.603035]
> -> #2 (&q->q_usage_counter(io)#3){++++}-{0:0}:
> [ 5.603038] blk_alloc_queue+0x319/0x350
> [ 5.603041] blk_mq_alloc_queue+0x63/0xd0
The above one is solved in for-6.14/block of block tree:
block: track queue dying state automatically for modeling queue freeze lockdep
q->q_usage_counter(io) is killed because disk isn't up yet.
If you apply the noio patch against for-6.1/block, the two splats should
have disappeared. If not, please post lockdep log.
Thanks,
Ming
next prev parent reply other threads:[~2025-01-13 9:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 10:12 Blockdev 6.13-rc lockdep splat regressions Thomas Hellström
2025-01-10 10:14 ` Christoph Hellwig
2025-01-10 10:21 ` Thomas Hellström
2025-01-10 12:13 ` Ming Lei
2025-01-10 14:36 ` Thomas Hellström
2025-01-11 3:05 ` Ming Lei
2025-01-12 11:33 ` Thomas Hellström
2025-01-12 15:50 ` Ming Lei
2025-01-12 17:44 ` Thomas Hellström
2025-01-13 0:55 ` Ming Lei
2025-01-13 8:48 ` Thomas Hellström
2025-01-13 9:28 ` Ming Lei [this message]
2025-01-13 9:58 ` Thomas Hellström
2025-01-13 10:40 ` Ming Lei
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=Z4TcvNCBXcLJV3vs@fedora \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=thomas.hellstrom@linux.intel.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).