[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6b933c16-5ddb-4b09-b367-3cf42ae94304@amd.com>
Date: Tue, 18 Jun 2024 13:42:56 +0200
From: Christian König <christian.koenig@....com>
To: Pavel Machek <pavel@...x.de>, Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Jesse Zhang <jesse.zhang@....com>, Alex Deucher <alexander.deucher@....com>,
Xinhui.Pan@....com, airlied@...il.com, daniel@...ll.ch,
Felix.Kuehling@....com, shashank.sharma@....com, guchun.chen@....com,
Philip.Yang@....com, mukul.joshi@....com, xiaogang.chen@....com,
amd-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH AUTOSEL 6.1 13/14] drm/amdgpu: fix dereference null return
value for the function amdgpu_vm_pt_parent
Am 18.06.24 um 11:11 schrieb Pavel Machek:
> Hi!
>
>> [ Upstream commit a0cf36546cc24ae1c95d72253c7795d4d2fc77aa ]
>>
>> The pointer parent may be NULLed by the function amdgpu_vm_pt_parent.
>> To make the code more robust, check the pointer parent.
> If this can happen, it should not WARN().
>
> If this can not happen, we don't need the patch in stable.
Right, that patch shouldn't be backported in any way.
Regards,
Christian.
>
> Best regards,
> Pavel
>
Powered by blists - more mailing lists