[<prev] [next>] [day] [month] [year] [list]
Message-ID: <344bcc64-bf13-4726-8530-48eca7d643d1@stanley.mountain>
Date: Sat, 12 Apr 2025 17:28:39 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: "Yadav, Arvind" <arvyadav@....com>
Cc: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@....com>,
Alex Deucher <alexander.deucher@....com>,
Christian König <christian.koenig@....com>,
David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
Arvind Yadav <Arvind.Yadav@....com>,
Shashank Sharma <shashank.sharma@....com>,
amd-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH next] drm/amdgpu: Fix double free in
amdgpu_userq_fence_driver_alloc()
On Thu, Apr 10, 2025 at 10:29:31PM +0530, Yadav, Arvind wrote:
> Please change this also instead of 'goto free_fence_drv' just return err.
>
> fence_drv = kzalloc(sizeof(*fence_drv), GFP_KERNEL);
> if (!fence_drv) {
> DRM_ERROR("Failed to allocate memory for fence driver\n");
> r = -ENOMEM;
> goto free_fence_drv; // this should be replace by return.
> }
>
> ~arvind
I noticed that when I was writing my patch as well. I'm always in favor
of direct returns, but it makes the patch confusing to add this unrelated
cleanup... I'll send it as a separate patch.
regards,
dan carpenter
Powered by blists - more mailing lists