[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5a073b2b-5102-adec-84dd-b62dc48c7451@web.de>
Date: Sun, 31 May 2020 11:00:17 +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: drm/nouveau/clk/gm20b: Fix memory leak in gm20b_clk_new()
> I just found that clk is referenced by pclk in this function. When clk is freed,
> pclk will be allocated in gm20b_clk_new_speedo0(). Thus we should not release clk
> in this function and there is no bug here.
Can there be a need to release a clock object after a failed gk20a_clk_ctor() call?
Regards,
Markus
Powered by blists - more mailing lists