[<prev] [next>] [day] [month] [year] [list]
Message-ID: <c966b91e-765f-c36c-2563-4e348fd1daf6@web.de>
Date: Fri, 19 Jun 2020 14:15:32 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Bernard Zhao <bernard@...o.com>, amd-gfx@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org
Cc: opensource.kernel@...o.com, Aditya Pakki <pakki001@....edu>,
Kangjie Lu <kjlu@....edu>, Navid Emamdoost <emamd001@....edu>,
Qiushi Wu <wu000273@....edu>, kernel-janitors@...r.kernel.org,
linux-kernel@...r.kernel.org,
Alex Deucher <alexander.deucher@....com>,
Christian König <christian.koenig@....com>,
Felix Kühling <Felix.Kuehling@....com>,
Daniel Vetter <daniel@...ll.ch>,
David Airlie <airlied@...ux.ie>
Subject: Re: [PATCH] drm/amdkfd: Fix memory leaks according to error branches
> The function kobject_init_and_add alloc memory like:
> kobject_init_and_add->kobject_add_varg->kobject_set_name_vargs
> ->kvasprintf_const->kstrdup_const->kstrdup->kmalloc_track_caller
> ->kmalloc_slab, in err branch this memory not free. If use
> kmemleak, this path maybe catched.
> These changes are to add kobject_put in kobject_init_and_add
> failed branch, fix potential memleak.
I suggest to improve this change description.
* Can an other wording variant be nicer?
* Will the tag “Fixes” become helpful?
Regards,
Markus
Powered by blists - more mailing lists