From: "Christian König" <christian.koenig@amd.com>
To: "Timur Kristóf" <timur.kristof@gmail.com>,
stable@vger.kernel.org, "Robert Garcia" <rob_garcia@163.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Pan Xinhui <Xinhui.Pan@amd.com>, David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yifan Zha <Yifan.Zha@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.1.y] drm/amdgpu: remove two invalid BUG_ON()s
Date: Wed, 22 Apr 2026 16:11:15 +0200 [thread overview]
Message-ID: <6064b45a-b8de-4848-856f-383d2d06680d@amd.com> (raw)
In-Reply-To: <7260936.9J7NaK4W3v@timur-hyperion>
Those points are certainly valid.
I've also up-streamed a patch which completely rejects userspace submissions who try to use the CE.
The problem is that those BUG_ON() can lead to a deny of service because they crash the whole kernel.
A BUG_ON() is only justified if it prevents even worse things to happen, e.g. data corruption or it would crash later on anyway just not so obvious on what is wrong.
Otherwise we should use WARN_ON().
Regards,
Christian.
On 4/22/26 16:03, Timur Kristóf wrote:
> Hi,
>
> In my opinion, this BUG_ON should NOT be removed.
>
> Using the CE was never well-supported by amdgpu and can lead to serious
> issues, so we are planning to remove it entirely. Userspace isn't using it, so
> there is no loss of functionality here.
>
> Mesa (the official userspace drivers) have never used CE and never will.
>
> Best regards,
> Timur
>
> On Friday, April 17, 2026 9:40:10 AM Central European Summer Time Robert
> Garcia wrote:
>> From: Christian König <christian.koenig@amd.com>
>>
>> [ Upstream commit 5d55ed19d4190d2c210ac05ac7a53f800a8c6fe5 ]
>>
>> Those can be triggered trivially by userspace.
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
>> Acked-by: Timur Kristóf <timur.kristof@gmail.com>
>> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>> [ Modified to gfx_v11_0.c only. ]
>> Signed-off-by: Robert Garcia <rob_garcia@163.com>
>> ---
>> drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
>> b/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c index 37f793f7d4d2..6e3a32779168
>> 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
>> @@ -5380,8 +5380,6 @@ static void gfx_v11_0_ring_emit_ib_gfx(struct
>> amdgpu_ring *ring, unsigned vmid = AMDGPU_JOB_GET_VMID(job);
>> u32 header, control = 0;
>>
>> - BUG_ON(ib->flags & AMDGPU_IB_FLAG_CE);
>> -
>> header = PACKET3(PACKET3_INDIRECT_BUFFER, 2);
>>
>> control |= ib->length_dw | (vmid << 24);
>
>
>
>
prev parent reply other threads:[~2026-04-22 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 7:40 [PATCH 6.1.y] drm/amdgpu: remove two invalid BUG_ON()s Robert Garcia
2026-04-20 13:21 ` Sasha Levin
2026-04-22 14:03 ` Timur Kristóf
2026-04-22 14:11 ` Christian König [this message]
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=6064b45a-b8de-4848-856f-383d2d06680d@amd.com \
--to=christian.koenig@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=Yifan.Zha@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob_garcia@163.com \
--cc=stable@vger.kernel.org \
--cc=timur.kristof@gmail.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