From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Gaosheng Cui <cuigaosheng1@huawei.com>, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, gongruiqi1@huawei.com,
wangweiyang2@huawei.com
Subject: Re: [PATCH -next,v2] nvmem: core: Fix memleak in nvmem_register()
Date: Mon, 18 Jul 2022 12:44:45 +0100 [thread overview]
Message-ID: <9029caa7-beea-34f6-7f9b-b2b230c3baeb@linaro.org> (raw)
In-Reply-To: <20220716095257.2752110-1-cuigaosheng1@huawei.com>
On 16/07/2022 10:52, Gaosheng Cui wrote:
> dev_set_name will alloc memory for nvmem->dev.kobj.name in
> nvmem_register, when nvmem_validate_keepouts failed, nvmem's
> memory will be freed and return, but nobody will free memory
> for nvmem->dev.kobj.name, there will be memleak, so moving
> dev_set_name after nvmem_validate_keepouts to fix it.
>
> Fixes: de0534df9347 ("nvmem: core: fix error handling while validating keepout regions")
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
> ---
> drivers/nvmem/core.c | 28 ++++++++++++++--------------
> 1 file changed, 14 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> index 1e3c754efd0d..a5d75edf509d 100644
> --- a/drivers/nvmem/core.c
> +++ b/drivers/nvmem/core.c
> @@ -808,20 +808,6 @@ struct nvmem_device *nvmem_register(const struct nvmem_config *config)
> else if (!config->no_of_node)
> nvmem->dev.of_node = config->dev->of_node;
>
> - switch (config->id) {
> - case NVMEM_DEVID_NONE:
> - dev_set_name(&nvmem->dev, "%s", config->name);
> - break;
> - case NVMEM_DEVID_AUTO:
> - dev_set_name(&nvmem->dev, "%s%d", config->name, nvmem->id);
> - break;
> - default:
> - dev_set_name(&nvmem->dev, "%s%d",
> - config->name ? : "nvmem",
> - config->name ? config->id : nvmem->id);
> - break;
> - }
> -
> nvmem->read_only = device_property_present(config->dev, "read-only") ||
> config->read_only || !nvmem->reg_write;
>
> @@ -838,6 +824,20 @@ struct nvmem_device *nvmem_register(const struct nvmem_config *config)
> }
> }
>
> + switch (config->id) {
> + case NVMEM_DEVID_NONE:
> + dev_set_name(&nvmem->dev, "%s", config->name);
> + break;
> + case NVMEM_DEVID_AUTO:
> + dev_set_name(&nvmem->dev, "%s%d", config->name, nvmem->id);
> + break;
> + default:
> + dev_set_name(&nvmem->dev, "%s%d",
> + config->name ? : "nvmem",
> + config->name ? config->id : nvmem->id);
> + break;
> + }
> +
The issue with this approach is that dev_err messages in
nvmem_validate_keepouts() will show up without device name setup.
I think better option is to move nvmem_validate_keepouts() after
device_register() and let the device core deal with cleaning name in
error cases.
--srini
> dev_dbg(&nvmem->dev, "Registering nvmem device %s\n", config->name);
>
> rval = device_register(&nvmem->dev);
next prev parent reply other threads:[~2022-07-18 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 9:52 Gaosheng Cui
2022-07-18 11:44 ` Srinivas Kandagatla [this message]
2022-07-18 12:29 ` cuigaosheng
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=9029caa7-beea-34f6-7f9b-b2b230c3baeb@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=cuigaosheng1@huawei.com \
--cc=gongruiqi1@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangweiyang2@huawei.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®