From: "John B. Moore" <jbmoore61@gmail.com>
To: alexander.deucher@amd.com, christian.koenig@amd.com
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
airlied@gmail.com, simona@ffwll.ch, stable@vger.kernel.org,
"John B. Moore" <jbmoore61@gmail.com>
Subject: [PATCH v2 0/2] drm/amdgpu: reject misaligned IB addresses in CS parser
Date: Fri, 24 Apr 2026 09:08:14 -0500 [thread overview]
Message-ID: <20260424140816.43766-1-jbmoore61@gmail.com> (raw)
Userspace can submit command streams with IB addresses whose low two
bits are set. On all hardware that amdgpu supports, those bits are
reserved (they encoded byte-swap mode on pre-amdgpu legacy HW).
Today these addresses pass through the CS parser unchecked and hit
BUG_ON(addr & 0x3) assertions in ring emission callbacks across
gfx_v9 through gfx_v12 and sdma_v4 through sdma_v7 (35 call sites),
crashing the kernel.
Patch 1 adds an early -EINVAL rejection in the CS parser before the
IB is allocated, plus a defense-in-depth WARN_ON_ONCE in
amdgpu_ib_schedule() to catch any that slip through from other code
paths.
Patch 2 is a trivial cleanup: removing a dead BUG_ON(!bo_va) in
amdgpu_cs_vm_handling() that is unreachable due to the NULL check on
the line above.
A follow-up series could convert the 35 downstream BUG_ON(addr & 0x3)
assertions in the ring emit_ib callbacks to WARN_ON_ONCE, but that is
a larger change and is not included here.
v2:
- Rebased onto amd-staging-drm-next (was incorrectly based on a
local branch in v1 — thanks Christian for catching this)
- Split the dead-code BUG_ON removal into a separate patch
- Moved the check before amdgpu_ib_get() to avoid unnecessary
IB allocation on bad input
- Added Fixes: tag and Cc: stable
John B. Moore (2):
drm/amdgpu: reject IB addresses with reserved byte-swap bits
drm/amdgpu: remove superfluous BUG_ON in amdgpu_cs_vm_handling
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 9 ++++++++-
drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c | 10 ++++++++++
2 files changed, 18 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2026-04-24 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 14:08 John B. Moore [this message]
2026-04-24 14:08 ` [PATCH v2 1/2] drm/amdgpu: reject IB addresses with reserved byte-swap bits John B. Moore
2026-04-27 7:13 ` Christian König
2026-04-24 14:08 ` [PATCH v2 2/2] drm/amdgpu: remove superfluous BUG_ON in amdgpu_cs_vm_handling John B. Moore
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=20260424140816.43766-1-jbmoore61@gmail.com \
--to=jbmoore61@gmail.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=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
/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