From: Nilay Shroff <nilay@linux.ibm.com>
To: Tejun Heo <tj@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>, Jens Axboe <axboe@kernel.dk>,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Ming Lei <ming.lei@redhat.com>
Subject: Re: [RESEND] Circular locking dependency involving, elevator_lock, rq_qos_mutex and pcpu_alloc_mutex
Date: Thu, 1 May 2025 22:50:30 +0530 [thread overview]
Message-ID: <03cf3cd2-8ddc-45ed-81ee-3cf8537f4163@linux.ibm.com> (raw)
In-Reply-To: <aBOosuedqt15xS1K@slm.duckdns.org>
On 5/1/25 10:30 PM, Tejun Heo wrote:
> Hello,
>
> On Tue, Apr 08, 2025 at 12:32:50PM +0530, Nilay Shroff wrote:
>> Thanks for the report! This is now a known issue. And we're currently working on
>> it to cut dependency of q->io_lockdep_map (or queue freeze-lock) on q->elevator_lock.
>> Please see below :https://lore.kernel.org/linux-block/67e6b425.050a0220.2f068f.007b.GAE@google.com/
>> https://lore.kernel.org/all/20250403105402.1334206-1-ming.lei@redhat.com/
>
> Any progress on this? The last activity on the threads seems to be back on
> Apr 10th and we're getting close to rc5. If we need to revert, I think it's
> about time to decide.
>
> Thanks.
>
This is currently actively being worked upon.
Please see here : https://lore.kernel.org/all/20250430043529.1950194-1-ming.lei@redhat.com/
We expect it to be soon ready for merge.
Thanks,
--Nilay
prev parent reply other threads:[~2025-05-01 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Z_QjW7zJLsuO0xp6@slm.duckdns.org>
2025-04-07 19:13 ` [RESEND] Circular locking dependency involving, elevator_lock, rq_qos_mutex and pcpu_alloc_mutex Tejun Heo
2025-04-08 7:02 ` Nilay Shroff
2025-05-01 17:00 ` Tejun Heo
2025-05-01 17:20 ` Nilay Shroff [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=03cf3cd2-8ddc-45ed-81ee-3cf8537f4163@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=hch@lst.de \
--cc=kuba@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=tj@kernel.org \
/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