From: David Carlier <devnexen@gmail.com>
To: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>
Cc: Mukul Joshi <mukul.joshi@amd.com>,
Felix Kuehling <felix.kuehling@amd.com>,
Philip Yang <Philip.Yang@amd.com>,
Lijo Lazar <lijo.lazar@amd.com>, David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, David Carlier <devnexen@gmail.com>
Subject: [PATCH] drm/amdgpu: Fix NPA-REVOKE racing an in-flight UALink import
Date: Sat, 26 Sep 2026 18:16:00 +0100 [thread overview]
Message-ID: <20260926171625.288519-1-devnexen@gmail.com> (raw)
The exporter records an importer when it answers NPA-REQ, so it can send
NPA-REVOKE as soon as the BO is freed, before the importer has finished
building the dma-buf for that handle. The revoke handler assumes a fully
imported node: it dereferences imp_xa_node->dmabuf, which is still NULL
until the import completes, and drops the xarray reference the importing
thread still relies on. The importer then links the node and marks it
READY regardless, so the node can be freed while still on the per-remote
list.
When the revoke hits a node that is still NOT_READY or PENDING, only
mark it for teardown and send NPA-RELEASE, as nothing has been handed to
user-space yet. The importer checks for teardown under the xarray lock
before linking the node and marking it READY, and unwinds otherwise.
Fixes: 7cc82cd90d35 ("drm/amdgpu: Implement mechanism to revoke exported memory")
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: David Carlier <devnexen@gmail.com>
---
Found by code analysis; not tested on hardware (needs two UALink-connected
accelerators in a vPod). Compile-tested with W=1. Applies on next-20260925
and does not overlap with Mukul's "UALink fixes" v2 series.
drivers/gpu/drm/amd/amdgpu/amdgpu_ualink.c | 30 +++++++++++++++++++---
1 file changed, 26 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ualink.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ualink.c
index 8411ea17172f..90d2a525ff5f 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ualink.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ualink.c
@@ -3265,6 +3265,7 @@ static void amdgpu_ualink_process_npa_revoke_msg(struct amdgpu_device *adev,
{
struct amdgpu_ualink_imp_xa_node *imp_xa_node;
struct amdgpu_bo *bo;
+ u32 node_state;
int r = 0;
/* Remove the entry from the Xarray. */
@@ -3288,7 +3289,19 @@ static void amdgpu_ualink_process_npa_revoke_msg(struct amdgpu_device *adev,
return;
}
+ node_state = READ_ONCE(imp_xa_node->node_state);
WRITE_ONCE(imp_xa_node->node_state, AMDGPU_UALINK_NODE_TEARDOWN);
+
+ /* The import is still in flight: the dmabuf may not exist yet and
+ * nothing has been handed to user-space. Leave the node to the
+ * importing thread, which sees the teardown state and unwinds.
+ */
+ if (node_state == AMDGPU_UALINK_NODE_NOT_READY ||
+ node_state == AMDGPU_UALINK_NODE_PENDING) {
+ xa_unlock(&adev->ualink.imp_xa);
+ goto send_release;
+ }
+
list_del_init(&imp_xa_node->list);
xa_unlock(&adev->ualink.imp_xa);
@@ -3299,6 +3312,7 @@ static void amdgpu_ualink_process_npa_revoke_msg(struct amdgpu_device *adev,
/* Drop the refcount for the node */
amdgpu_ualink_imp_xa_entry_put(imp_xa_node);
+send_release:
r = amdgpu_ualink_send_npa_release_msg(adev, remote_acc_id, handle);
if (r)
dev_err(adev->dev,
@@ -3760,9 +3774,20 @@ static int amdgpu_ualink_do_import_handle(struct amdgpu_device *adev,
return r;
}
- /* Add this node to the imported handles list for the remote GPU */
+ /* Add this node to the imported handles list for the remote GPU,
+ * unless the exporter revoked the handle while the import was in
+ * flight. The dmabuf is released with the last node reference.
+ */
xa_lock(&adev->ualink.imp_xa);
+ if (READ_ONCE(imp_xa_node->node_state) == AMDGPU_UALINK_NODE_TEARDOWN) {
+ xa_unlock(&adev->ualink.imp_xa);
+ dev_warn(adev->dev,
+ "IMPORT: handle:%llx:%llx revoked during import\n",
+ handle.handle_hi, handle.handle_lo);
+ return -EINVAL;
+ }
list_add(&imp_xa_node->list, &adev->ualink.imp_handles_list[remote_acc_id]);
+ WRITE_ONCE(imp_xa_node->node_state, AMDGPU_UALINK_NODE_READY);
xa_unlock(&adev->ualink.imp_xa);
return 0;
@@ -3938,9 +3963,6 @@ int amdgpu_ualink_import_handle(struct drm_device *dev,
"IMPORT: XA import failed for handle:%llx:%llx\n",
handle.handle_hi, handle.handle_lo);
goto cleanup;
- } else {
- WRITE_ONCE(imp_xa_node->node_state,
- AMDGPU_UALINK_NODE_READY);
}
}
--
2.55.0
reply other threads:[~2026-09-26 17:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260926171625.288519-1-devnexen@gmail.com \
--to=devnexen@gmail.com \
--cc=Philip.Yang@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=lijo.lazar@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mukul.joshi@amd.com \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®