From: cuigaosheng <cuigaosheng1@huawei.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
<gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <gongruiqi1@huawei.com>,
<wangweiyang2@huawei.com>
Subject: Re: [PATCH -next,v4] nvmem: core: Fix memleak in nvmem_register()
Date: Mon, 18 Jul 2022 20:43:08 +0800 [thread overview]
Message-ID: <be2bffa9-7331-9d96-e7a0-94561c66d00d@huawei.com> (raw)
In-Reply-To: <a1b7262a-2c9d-7495-e660-b6ef43d3ad44@linaro.org>
>
> What changed since v3?
I adjusted the commit message because the implementation of the code has
changed.
>
> Unnecessary braces here.
Already fixed.
Thanks,
在 2022/7/18 20:24, Srinivas Kandagatla 写道:
>
>
> On 18/07/2022 13:21, 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
>> nvmem_validate_keepouts() after device_register() and let
>> the device core deal with cleaning name in error cases.
>>
>> Fixes: de0534df9347 ("nvmem: core: fix error handling while
>> validating keepout regions")
>> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
>> ---
>
> What changed since v3?
>
>> drivers/nvmem/core.c | 16 +++++++---------
>> 1 file changed, 7 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
>> index 1e3c754efd0d..6067d3bbff5d 100644
>> --- a/drivers/nvmem/core.c
>> +++ b/drivers/nvmem/core.c
>> @@ -829,21 +829,19 @@ struct nvmem_device *nvmem_register(const
>> struct nvmem_config *config)
>> nvmem->dev.groups = nvmem_dev_groups;
>> #endif
>> - if (nvmem->nkeepout) {
>> - rval = nvmem_validate_keepouts(nvmem);
>> - if (rval) {
>> - ida_free(&nvmem_ida, nvmem->id);
>> - kfree(nvmem);
>> - return ERR_PTR(rval);
>> - }
>> - }
>> -
>> dev_dbg(&nvmem->dev, "Registering nvmem device %s\n",
>> config->name);
>> rval = device_register(&nvmem->dev);
>> if (rval)
>> goto err_put_device;
>> + if (nvmem->nkeepout) {
>> + rval = nvmem_validate_keepouts(nvmem);
>> + if (rval) {
>
> Unnecessary braces here.
>
> --srini
>> + goto err_device_del;
>> + }
>> + }
>> +
>> if (config->compat) {
>> rval = nvmem_sysfs_setup_compat(nvmem, config);
>> if (rval)
> .
prev parent reply other threads:[~2022-07-18 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 12:21 Gaosheng Cui
2022-07-18 12:24 ` Srinivas Kandagatla
2022-07-18 12:43 ` cuigaosheng [this message]
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=be2bffa9-7331-9d96-e7a0-94561c66d00d@huawei.com \
--to=cuigaosheng1@huawei.com \
--cc=gongruiqi1@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.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®