lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 31 May 2020 10:03:19 +0200 From: Markus Elfring <Markus.Elfring@....de> To: Dinghao Liu <dinghao.liu@....edu.cn>, dri-devel@...ts.freedesktop.org, nouveau@...ts.freedesktop.org Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org, Ben Skeggs <bskeggs@...hat.com>, David Airlie <airlied@...ux.ie>, Kangjie Lu <kjlu@....edu> Subject: Re: [PATCH] drm/nouveau/clk/gm20b: Fix memory leak in gm20b_clk_new() > When gk20a_clk_ctor() returns an error code, pointer "clk" > should be released. Such an information is reasonable. > It's the same when gm20b_clk_new() returns from elsewhere following this call. I suggest to reconsider the interpretation of the software situation once more. Can it be that the allocated clock object should be kept usable even after a successful return from this function? Would you like to add the tag “Fixes” to the commit message? Regards, Markus
Powered by blists - more mailing lists