From: Markus Elfring <Markus.Elfring@web.de>
To: Ruihai Zhou <zhou.ruihai@qq.com>,
kernel-janitors@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Markus Schneider-Pargmann <msp@baylibre.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvmem: core: Fix memleak in nvmem_add_cells_from_dt error path
Date: Wed, 11 Sep 2024 15:05:20 +0200 [thread overview]
Message-ID: <aca066e5-8f8c-4c08-8c8c-8743e98ff7f7@web.de> (raw)
In-Reply-To: <tencent_C3AF1A5AA6C84EC8AFBC9434383912612209@qq.com>
…
> 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
next prev parent reply other threads:[~2024-09-11 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 12:06 Ruihai Zhou
2024-09-11 12:27 ` Greg KH
2024-09-11 13:05 ` Markus Elfring [this message]
2024-09-11 13:09 ` Greg Kroah-Hartman
2024-09-11 19:46 ` Markus Schneider-Pargmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aca066e5-8f8c-4c08-8c8c-8743e98ff7f7@web.de \
--to=markus.elfring@web.de \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=zhou.ruihai@qq.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®