From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: "Christian König" <christian.koenig@amd.com>,
"Tvrtko Ursulin" <tvrtko.ursulin@igalia.com>,
"Philipp Stanner" <phasta@kernel.org>,
"Boris Brezillon" <boris.brezillon@collabora.com>
Subject: [PATCH 2/2] dma-buf: Assign separate lockdep class to array lock
Date: Tue, 24 Feb 2026 09:55:44 -0800 [thread overview]
Message-ID: <20260224175544.2167712-2-matthew.brost@intel.com> (raw)
In-Reply-To: <20260224175544.2167712-1-matthew.brost@intel.com>
dma_fence_array_enable_signaling() runs while holding the array
inline_lock and may add callbacks to underlying fences, which takes
their inline_lock.
Since both locks share the same lockdep class, this valid nesting
triggers a recursive locking warning. Assign a distinct lockdep class
to the array inline_lock so lockdep can correctly model the hierarchy.
Fixes: 5943243914b9 ("dma-buf: use inline lock for the dma-fence-array")
Cc: Christian König <christian.koenig@amd.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Cc: Philipp Stanner <phasta@kernel.org>
Cc: Boris Brezillon <boris.brezillon@collabora.com>
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
---
drivers/dma-buf/dma-fence-array.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/drivers/dma-buf/dma-fence-array.c b/drivers/dma-buf/dma-fence-array.c
index cd970eceaefb..9cfac1ca68b5 100644
--- a/drivers/dma-buf/dma-fence-array.c
+++ b/drivers/dma-buf/dma-fence-array.c
@@ -200,6 +200,10 @@ void dma_fence_array_init(struct dma_fence_array *array,
u64 context, unsigned seqno,
bool signal_on_any)
{
+#if IS_ENABLED(CONFIG_LOCKDEP)
+ static struct lock_class_key dma_fence_array_lock_key;
+#endif
+
WARN_ON(!num_fences || !fences);
array->num_fences = num_fences;
@@ -208,6 +212,20 @@ void dma_fence_array_init(struct dma_fence_array *array,
seqno);
init_irq_work(&array->work, irq_dma_fence_array_work);
+#if IS_ENABLED(CONFIG_LOCKDEP)
+ /*
+ * dma_fence_array_enable_signaling() is invoked while holding
+ * array->base.inline_lock and may call dma_fence_add_callback()
+ * on the underlying fences, which takes their inline_lock.
+ *
+ * Since both locks share the same lockdep class, this legitimate
+ * nesting confuses lockdep and triggers a recursive locking
+ * warning. Assign a separate lockdep class to the array lock
+ * to model this hierarchy correctly.
+ */
+ lockdep_set_class(&array->base.inline_lock, &dma_fence_array_lock_key);
+#endif
+
atomic_set(&array->num_pending, signal_on_any ? 1 : num_fences);
array->fences = fences;
--
2.34.1
next prev parent reply other threads:[~2026-02-24 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 17:55 [PATCH 1/2] dma-buf: Assign separate lockdep class to chain lock Matthew Brost
2026-02-24 17:55 ` Matthew Brost [this message]
2026-02-25 8:26 ` Christian König
2026-03-02 15:28 ` Boris Brezillon
2026-03-02 15:42 ` Christian König
2026-03-02 16:39 ` Boris Brezillon
2026-03-02 20:05 ` Matthew Brost
2026-03-03 8:36 ` Boris Brezillon
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=20260224175544.2167712-2-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=boris.brezillon@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=phasta@kernel.org \
--cc=tvrtko.ursulin@igalia.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