diff options
| author | Amir Shetaia <Amir.Shetaia@amd.com> | 2026-04-10 17:38:13 +0300 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2026-04-17 21:47:48 +0300 |
| commit | ad52d61d82181dbdb7f05826de38352d5e550cc2 (patch) | |
| tree | f6dfc5fc752f77c98170b5c3e5ed24da3028869d /scripts/kernel-doc | |
| parent | 08cdf07b55bff236aeaea3d52a8d1ffe11d801ec (diff) | |
| download | linux-ad52d61d82181dbdb7f05826de38352d5e550cc2.tar.xz | |
drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure
KFD VRAM allocations set AMDGPU_GEM_CREATE_VRAM_WIPE_ON_RELEASE
but not AMDGPU_GEM_CREATE_VRAM_CLEARED, leaving freshly allocated
VRAM with stale data from prior use observable by compute kernels.
The GEM ioctl path already sets VRAM_CLEARED for all userspace
allocations via amdgpu_gem_create_ioctl() and
amdgpu_mode_dumb_create(). The KFD path was missing this flag,
allowing stale page table remnants to leak into user buffers.
This causes crashes in RCCL P2P transport where non-zero data in
ptrExchange/head/tail fields corrupts the protocol handshake.
Signed-off-by: Amir Shetaia <Amir.Shetaia@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org
Diffstat (limited to 'scripts/kernel-doc')
0 files changed, 0 insertions, 0 deletions
