Am 15.03.24 um 15:12 schrieb Alex Deucher:
On Fri, Mar 15, 2024 at 10:12 AM Christian König
wrote:
Am 15.03.24 um 03:39 schrieb vitaly.pros...@amd.com:
From: Vitaly Prosyak
The bug can be triggered by sending an amdgpu_cs_wait_ioctl
to the AMDGPU DRM driver on any ASICs with valid context.
T
On Fri, Mar 15, 2024 at 10:12 AM Christian König
wrote:
>
> Am 15.03.24 um 03:39 schrieb vitaly.pros...@amd.com:
> > From: Vitaly Prosyak
> >
> > The bug can be triggered by sending an amdgpu_cs_wait_ioctl
> > to the AMDGPU DRM driver on any ASICs with valid context.
> > The bug was reported by J
Am 15.03.24 um 03:39 schrieb vitaly.pros...@amd.com:
From: Vitaly Prosyak
The bug can be triggered by sending an amdgpu_cs_wait_ioctl
to the AMDGPU DRM driver on any ASICs with valid context.
The bug was reported by Joonkyo Jung .
For example the following code:
static void Syzkaller2(int
From: Vitaly Prosyak
The bug can be triggered by sending an amdgpu_cs_wait_ioctl
to the AMDGPU DRM driver on any ASICs with valid context.
The bug was reported by Joonkyo Jung .
For example the following code:
static void Syzkaller2(int fd)
{
union drm_amdgpu_ctx arg1;
un
From: Vitaly Prosyak
The bug can be triggered by sending an amdgpu_cs_wait_ioctl
to the AMDGPU DRM driver on any ASICs with valid context.
The bug was reported by Joonkyo Jung .
For example the following code:
static void Syzkaller2(int fd)
{
union drm_amdgpu_ctx arg1;
un
