From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
linux-kernel@vger.kernel.org, Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH] sched_ext: Fix potential deadlock in destroy_dsq()
Date: Thu, 16 Jan 2025 16:06:26 -1000 [thread overview]
Message-ID: <Z4m7Iq_eiTZmASd_@slm.duckdns.org> (raw)
In-Reply-To: <20250116115101.549175-1-arighi@nvidia.com>
On Thu, Jan 16, 2025 at 12:51:01PM +0100, Andrea Righi wrote:
> When creating and destroying DSQs concurrently, a potential deadlock can
> occur due to a circular locking dependency between the locks involved in
> the operations:
>
> - create_dsq():
>
> rhashtable_bucket --> rq->lock --> dsq->lock
Hmm... this is probably the same thing that Breno tried to fix with
rhashtable update. Breno, what's the current state of that patch? I saw bug
reports and fix patch flying by but didn't track them closely.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-01-17 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 11:51 [PATCH] sched_ext: Fix potential deadlock in destroy_dsq() Andrea Righi
2025-01-17 2:06 ` Tejun Heo [this message]
2025-01-17 9:46 ` Breno Leitao
2025-01-17 9:55 ` Andrea Righi
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=Z4m7Iq_eiTZmASd_@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=void@manifault.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.