From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: matthew.brost@intel.com
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: [PATCH] dma-buf: revert "use inline lock for the dma-fence-chain"
Date: Mon, 23 Feb 2026 20:57:05 +0100 [thread overview]
Message-ID: <20260223195705.206226-1-christian.koenig@amd.com> (raw)
This reverts commit a408c0ca0c411ca1ead995bdae3112a806c87556.
This causes a lockdep splat. Not really the right fix, but changing this
is more work than expected.
Signed-off-by: Christian König <christian.koenig@amd.com>
---
drivers/dma-buf/dma-fence-chain.c | 3 ++-
include/linux/dma-fence-chain.h | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/dma-buf/dma-fence-chain.c b/drivers/dma-buf/dma-fence-chain.c
index a707792b6025..a8a90acf4f34 100644
--- a/drivers/dma-buf/dma-fence-chain.c
+++ b/drivers/dma-buf/dma-fence-chain.c
@@ -245,6 +245,7 @@ void dma_fence_chain_init(struct dma_fence_chain *chain,
struct dma_fence_chain *prev_chain = to_dma_fence_chain(prev);
uint64_t context;
+ spin_lock_init(&chain->lock);
rcu_assign_pointer(chain->prev, prev);
chain->fence = fence;
chain->prev_seqno = 0;
@@ -260,7 +261,7 @@ void dma_fence_chain_init(struct dma_fence_chain *chain,
seqno = max(prev->seqno, seqno);
}
- dma_fence_init64(&chain->base, &dma_fence_chain_ops, NULL,
+ dma_fence_init64(&chain->base, &dma_fence_chain_ops, &chain->lock,
context, seqno);
/*
diff --git a/include/linux/dma-fence-chain.h b/include/linux/dma-fence-chain.h
index df3beadf1515..5cd3ba53b4a1 100644
--- a/include/linux/dma-fence-chain.h
+++ b/include/linux/dma-fence-chain.h
@@ -46,6 +46,7 @@ struct dma_fence_chain {
*/
struct irq_work work;
};
+ spinlock_t lock;
};
--
2.43.0
next reply other threads:[~2026-02-23 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 19:57 Christian König [this message]
2026-02-23 20:18 ` [PATCH] dma-buf: revert "use inline lock for the dma-fence-chain" Matthew Brost
2026-02-23 23:42 ` Claude review: " Claude Code Review Bot
2026-02-23 23:42 ` Claude Code Review Bot
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=20260223195705.206226-1-christian.koenig@amd.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.brost@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