[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <31187f41-64c8-d7ce-fcf2-5da421b3e194@igalia.com>
Date: Mon, 1 Aug 2022 14:06:41 -0300
From: André Almeida <andrealmeid@...lia.com>
To: Sebin Sebastian <mailmesebin00@...il.com>
Cc: Alex Deucher <alexander.deucher@....com>,
Christian König <christian.koenig@....com>,
"Pan, Xinhui" <Xinhui.Pan@....com>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
Nirmoy Das <nirmoy.das@....com>,
Lijo Lazar <lijo.lazar@....com>, Evan Quan <evan.quan@....com>,
Tom St Denis <tom.stdenis@....com>,
Somalapuram Amaranath <Amaranath.Somalapuram@....com>,
amd-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 -next] drm/amdgpu: double free error and freeing
uninitialized null pointer
Às 00:46 de 30/07/22, Sebin Sebastian escreveu:
> Fix a double free and an uninitialized pointer read error. Both tmp and
> new are pointing at same address and both are freed which leads to
> double free. Adding a check to verify if new and tmp are free in the
> error_free label fixes the double free issue. new is not initialized to
> null which also leads to a free on an uninitialized pointer.
>
> Suggested by: S. Amaranath <Amaranath.Somalapuram@....com>
> Signed-off-by: Sebin Sebastian <mailmesebin00@...il.com>
Reviewed-by: André Almeida <andrealmeid@...lia.com>
Powered by blists - more mailing lists