From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>,
Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: linux-kernel@vger.kernel.org, gongruiqi1@huawei.com,
wangweiyang2@huawei.com
Subject: Re: [PATCH -next] nvmem: core: Fix memleak in nvmem_register()
Date: Mon, 18 Jul 2022 12:40:53 +0100 [thread overview]
Message-ID: <595e0169-fe87-0477-fbe4-ff89387605df@linaro.org> (raw)
In-Reply-To: <YtJ1mthCP+4laqOn@kroah.com>
On 16/07/2022 09:23, Greg KH wrote:
> On Sat, Jul 16, 2022 at 03:53:52PM +0800, 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 using
>> kfree_const(nvmem->dev.kobj.name) 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 | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
>> index 1e3c754efd0d..6c75c9afa5f3 100644
>> --- a/drivers/nvmem/core.c
>> +++ b/drivers/nvmem/core.c
>> @@ -833,6 +833,7 @@ struct nvmem_device *nvmem_register(const struct nvmem_config *config)
>> rval = nvmem_validate_keepouts(nvmem);
>> if (rval) {
>> ida_free(&nvmem_ida, nvmem->id);
>> + kfree_const(nvmem->dev.kobj.name);
>> kfree(nvmem);
>
> Something is really wrong, you should never be touching the name pointer
> of a kobject directly like this. Also the device structure itself
> should be cleaning up the memory, not a kfree. So this feels wrong...
The problem is that at this point we have not device_intialize() the dev
yet, so there is no refcount setup for kobject yet.
I see two drivers (drivers/nvme/core.c and drivers/base/node.c) doing
something similar.
Most common (99.99%) usage pattern is
dev_set_name(...)
ret = device_register(..);
if (ret < 0)
put_device(..)
but in this particular case we have:
dev_set_name(...)
..
ret = do_some_error_checks()
if (ret < 0)
return ret;
...
ret = device_register(..);
if (ret < 0)
put_device(..)
One solution is to follow the most used pattern and move the checks
after device register and let device core take care of freeing this
kobj.name as part of its cleanup routine.
--srini
>
> greg k-h
prev parent reply other threads:[~2022-07-18 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 7:53 Gaosheng Cui
2022-07-16 8:23 ` Greg KH
2022-07-16 9:59 ` cuigaosheng
2022-07-18 11:40 ` Srinivas Kandagatla [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=595e0169-fe87-0477-fbe4-ff89387605df@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®