<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/git/next/linux-next.git/drivers/accel, branch master</title>
<subtitle>The linux-next integration testing tree</subtitle>
<id>https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/atom?h=master</id>
<link rel='self' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/'/>
<updated>2026-07-08T12:08:21+00:00</updated>
<entry>
<title>Merge branch 'for-linux-next' of https://gitlab.freedesktop.org/drm/misc/kernel.git</title>
<updated>2026-07-08T12:08:21+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2026-07-08T12:08:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b9216e7c47c7c5016f0d0f94508210fd76c07f26'/>
<id>urn:sha1:b9216e7c47c7c5016f0d0f94508210fd76c07f26</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'drm-next' of https://gitlab.freedesktop.org/drm/kernel.git</title>
<updated>2026-07-08T12:08:17+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2026-07-08T12:08:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=ae4cf658e93cf65191d8d04784abb711147bc989'/>
<id>urn:sha1:ae4cf658e93cf65191d8d04784abb711147bc989</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'for-linux-next-fixes' of https://gitlab.freedesktop.org/drm/misc/kernel.git</title>
<updated>2026-07-08T11:23:24+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2026-07-08T11:23:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=7f4a1d2c0c95f2ff840f7a9d5dd1907c1f9bb93e'/>
<id>urn:sha1:7f4a1d2c0c95f2ff840f7a9d5dd1907c1f9bb93e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>accel/amdxdna: Fix potential NULL pointer dereference of abo-&gt;client</title>
<updated>2026-07-08T03:49:28+00:00</updated>
<author>
<name>Lizhi Hou</name>
<email>lizhi.hou@amd.com</email>
</author>
<published>2026-07-07T20:15:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=c69dbbf0212734e22219dfc31c0922bd7c9ffbb0'/>
<id>urn:sha1:c69dbbf0212734e22219dfc31c0922bd7c9ffbb0</id>
<content type='text'>
Closing a BO handle clears abo-&gt;client, while the underlying GEM object
may remain alive due to internal kernel references. As a result, code
executed after the BO handle is closed may dereference a NULL abo-&gt;client
pointer.

Remove accesses to abo-&gt;client from code paths that may execute after the
BO handle has been closed.

Fixes: d76856beb4a4 ("accel/amdxdna: Refactor GEM BO handling and add helper APIs for address retrieval")
Reviewed-by: Max Zhen &lt;max.zhen@amd.com&gt;
Signed-off-by: Lizhi Hou &lt;lizhi.hou@amd.com&gt;
Link: https://patch.msgid.link/20260707201556.562191-1-lizhi.hou@amd.com
</content>
</entry>
<entry>
<title>accel/amdxdna: Check init_srcu_struct() return value</title>
<updated>2026-07-08T03:49:19+00:00</updated>
<author>
<name>Lizhi Hou</name>
<email>lizhi.hou@amd.com</email>
</author>
<published>2026-07-07T17:23:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=44d8fddf1c87d6bb6b65983041a0ce6c2af66bb9'/>
<id>urn:sha1:44d8fddf1c87d6bb6b65983041a0ce6c2af66bb9</id>
<content type='text'>
The return value of init_srcu_struct() is currently ignored. If
initialization fails, subsequent use of hwctx_srcu may result in invalid
memory accesses.

Check the return value of init_srcu_struct() and propagate the error to
the caller.

Fixes: aac243092b70 ("accel/amdxdna: Add command execution")
Reviewed-by: Mario Limonciello (AMD) &lt;superm1@kernel.org&gt;
Signed-off-by: Lizhi Hou &lt;lizhi.hou@amd.com&gt;
Link: https://patch.msgid.link/20260707172323.539721-1-lizhi.hou@amd.com
</content>
</entry>
<entry>
<title>accel/amdxdna: Check drmm_mutex_init() return value</title>
<updated>2026-07-08T03:49:10+00:00</updated>
<author>
<name>Lizhi Hou</name>
<email>lizhi.hou@amd.com</email>
</author>
<published>2026-07-07T17:23:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=0f092793a7b527dfb2cde323d4e5630d43447b84'/>
<id>urn:sha1:0f092793a7b527dfb2cde323d4e5630d43447b84</id>
<content type='text'>
drmm_mutex_init() may fail and return an error. Check the return value
and abort initialization if mutex creation fails.

Fixes: 8c9ff1b181ba ("accel/amdxdna: Add a new driver for AMD AI Engine")
Reviewed-by: Max Zhen &lt;max.zhen@amd.com&gt;
Signed-off-by: Lizhi Hou &lt;lizhi.hou@amd.com&gt;
Link: https://patch.msgid.link/20260707172307.539676-1-lizhi.hou@amd.com
</content>
</entry>
<entry>
<title>accel/amdxdna: Fix hardware context race in amdxdna_update_heap()</title>
<updated>2026-07-07T17:04:51+00:00</updated>
<author>
<name>Lizhi Hou</name>
<email>lizhi.hou@amd.com</email>
</author>
<published>2026-07-07T05:58:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=928caf71e566ddc5f303f15fb9c33f16a9915f30'/>
<id>urn:sha1:928caf71e566ddc5f303f15fb9c33f16a9915f30</id>
<content type='text'>
amdxdna_update_heap() iterates over hardware contexts while holding
xdna-&gt;dev_lock. During the iteration, amdxdna_pm_resume_get_locked() may
temporarily release and reacquire the lock, allowing hardware contexts to
be modified concurrently.

Fix the race by calling amdxdna_pm_resume_get_locked() before
iterating over hardware contexts.

Fixes: dbc8fd7a03cb ("accel/amdxdna: Add expandable device heap support")
Reviewed-by: Max Zhen &lt;max.zhen@amd.com&gt;
Signed-off-by: Lizhi Hou &lt;lizhi.hou@amd.com&gt;
Link: https://patch.msgid.link/20260707055818.479165-1-lizhi.hou@amd.com
</content>
</entry>
<entry>
<title>accel/amdxdna: Fix deadlock on debug BO command timeout</title>
<updated>2026-07-07T17:04:43+00:00</updated>
<author>
<name>Lizhi Hou</name>
<email>lizhi.hou@amd.com</email>
</author>
<published>2026-07-07T05:57:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=c8d2530791cb53602ac06ec2db6287d99f51cdbc'/>
<id>urn:sha1:c8d2530791cb53602ac06ec2db6287d99f51cdbc</id>
<content type='text'>
Both amdxdna_hwctx_sync_debug_bo() and amdxdna_drm_config_hwctx_ioctl()
hold xdna-&gt;dev_lock while invoking backend operations. If the hardware
hangs, aie2_cmd_wait() blocks waiting for a firmware response. When the
DRM scheduler timeout expires, aie2_sched_job_timedout() is invoked to
reset the hardware. However, the timeout handler also attempts to acquire
dev_lock, resulting in a deadlock.

Avoid this by releasing dev_lock before waiting for the firmware
response and reacquiring it after the wait completes. This allows the
timeout handler to proceed with device recovery when a debug BO command
times out.

Fixes: 7ea046838021 ("accel/amdxdna: Support firmware debug buffer")
Reviewed-by: Max Zhen &lt;max.zhen@amd.com&gt;
Signed-off-by: Lizhi Hou &lt;lizhi.hou@amd.com&gt;
Link: https://patch.msgid.link/20260707055732.479103-1-lizhi.hou@amd.com
</content>
</entry>
<entry>
<title>accel/amdxdna: fix open_ref leak and stale client pointer on dma map failure</title>
<updated>2026-07-07T17:04:34+00:00</updated>
<author>
<name>Lizhi Hou</name>
<email>lizhi.hou@amd.com</email>
</author>
<published>2026-07-07T05:56:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=66ff5c0eee02c4be67f8ba7fb6c63709ef1c92a3'/>
<id>urn:sha1:66ff5c0eee02c4be67f8ba7fb6c63709ef1c92a3</id>
<content type='text'>
amdxdna_gem_obj_open() increments open_ref before attempting to set up
the DMA address mapping.  When amdxdna_dma_map_bo() fails, the function
returned immediately without rolling back either change made on the first
open (open_ref == 1 path).

Fix it by decrementing open_ref and clearing abo-&gt;client on the error path.

Fixes: ece3e8980907 ("accel/amdxdna: Allow forcing IOVA-based DMA via module parameter")
Reviewed-by: Max Zhen &lt;max.zhen@amd.com&gt;
Signed-off-by: Lizhi Hou &lt;lizhi.hou@amd.com&gt;
Link: https://patch.msgid.link/20260707055658.479049-1-lizhi.hou@amd.com
</content>
</entry>
<entry>
<title>accel/amdxdna: Fix potential amdxdna_umap lifetime race</title>
<updated>2026-07-07T17:00:04+00:00</updated>
<author>
<name>Lizhi Hou</name>
<email>lizhi.hou@amd.com</email>
</author>
<published>2026-07-06T22:12:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=14f172eff9c19f8043a9858845f33cd034f3a41e'/>
<id>urn:sha1:14f172eff9c19f8043a9858845f33cd034f3a41e</id>
<content type='text'>
amdxdna_umap_release() calls the blocking mmu_interval_notifier_remove()
before removing the object from abo-&gt;mem.umap_list. If
aie2_populate_range() runs concurrently, it may obtain a reference to an
amdxdna_umap that is being released, leading to a potential use-after-free.

Use kref_get_unless_zero() in aie2_populate_range() when acquiring a
reference. If the reference count has already dropped to zero, release
is in progress and the entry is skipped.

Fixes: e486147c912f ("accel/amdxdna: Add BO import and export")
Reviewed-by: Max Zhen &lt;max.zhen@amd.com&gt;
Signed-off-by: Lizhi Hou &lt;lizhi.hou@amd.com&gt;
Link: https://patch.msgid.link/20260706221228.434099-1-lizhi.hou@amd.com
</content>
</entry>
</feed>
