[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Zp5W2GE3G3j-0bjP@sashalap>
Date: Mon, 22 Jul 2024 08:55:52 -0400
From: Sasha Levin <sashal@...nel.org>
To: Christian König <christian.koenig@....com>
Cc: Pavel Machek <pavel@...x.de>, 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
On Tue, Jun 18, 2024 at 01:42:56PM +0200, Christian König wrote:
>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.
I'll drop it, thanks!
--
Thanks,
Sasha
Powered by blists - more mailing lists