[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aca066e5-8f8c-4c08-8c8c-8743e98ff7f7@web.de>
Date: Wed, 11 Sep 2024 15:05:20 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Ruihai Zhou <zhou.ruihai@...com>, kernel-janitors@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Markus Schneider-Pargmann <msp@...libre.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] nvmem: core: Fix memleak in nvmem_add_cells_from_dt error
path
…
> is outside of the valid range, the info.name alloc by kasprintf will
allocated by kasprintf()?
> cause memleak. Just free before return from nvmem_add_cells_from_dt
…
a memory leak? ()?
How do you think about to increase the application of scope-based resource management?
Regards,
Markus
Powered by blists - more mailing lists