[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADnq5_OOWekUj-Y8Y64=vUUMfUmEXUyQ1Ougmqj2afKtu6hdNA@mail.gmail.com>
Date: Wed, 10 Aug 2022 12:41:11 -0400
From: Alex Deucher <alexdeucher@...il.com>
To: André Almeida <andrealmeid@...lia.com>
Cc: Sebin Sebastian <mailmesebin00@...il.com>,
Tom St Denis <tom.stdenis@....com>,
Lijo Lazar <lijo.lazar@....com>,
Somalapuram Amaranath <Amaranath.Somalapuram@....com>,
David Airlie <airlied@...ux.ie>,
"Pan, Xinhui" <Xinhui.Pan@....com>, linux-kernel@...r.kernel.org,
amd-gfx@...ts.freedesktop.org, Nirmoy Das <nirmoy.das@....com>,
dri-devel@...ts.freedesktop.org, Daniel Vetter <daniel@...ll.ch>,
Alex Deucher <alexander.deucher@....com>,
Evan Quan <evan.quan@....com>,
Christian König <christian.koenig@....com>
Subject: Re: [PATCHv2 -next] drm/amdgpu: double free error and freeing
uninitialized null pointer
Applied. Thanks!
Alex
On Mon, Aug 1, 2022 at 1:08 PM André Almeida <andrealmeid@...lia.com> wrote:
>
> À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