From: Yang Yingliang <yangyingliang@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <open-iscsi@googlegroups.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <lduncan@suse.com>,
<cleech@redhat.com>, <michael.christie@oracle.com>,
<jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<rafael@kernel.org>
Subject: Re: [PATCH] drivers: base: transport_class: fix possible memory leak
Date: Thu, 10 Nov 2022 16:44:16 +0800 [thread overview]
Message-ID: <d509e930-779b-866e-9b1f-d58db6abfc43@huawei.com> (raw)
In-Reply-To: <Y2yzwB0IuaVS3AVq@kroah.com>
Hi Greg,
On 2022/11/10 16:18, Greg KH wrote:
> On Thu, Nov 10, 2022 at 11:48:09AM +0800, Yang Yingliang wrote:
>> Current some drivers(like iscsi) call transport_register_device()
>> failed, they don't call transport_destroy_device() to release the
>> memory allocated in transport_setup_device(), because they don't
>> know what was done, it should be internal thing to release the
>> resource in register function. So fix this leak by calling destroy
>> function inside register function.
>>
>> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>> ---
>> include/linux/transport_class.h | 9 ++++++++-
>> 1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/linux/transport_class.h b/include/linux/transport_class.h
>> index 63076fb835e3..f4835250bbfc 100644
>> --- a/include/linux/transport_class.h
>> +++ b/include/linux/transport_class.h
>> @@ -70,8 +70,15 @@ void transport_destroy_device(struct device *);
>> static inline int
>> transport_register_device(struct device *dev)
>> {
>> + int ret;
>> +
>> transport_setup_device(dev);
>> - return transport_add_device(dev);
>> + ret = transport_add_device(dev);
>> + if (ret) {
>> + transport_destroy_device(dev);
>> + }
> Please use scripts/checkpatch.pl on your patches before sending them out
Sure, of course. :)
> so you don't get grumpy maintainers asking you to use
> scripts/checkpatch.pl on your patches :)
I sent a fix patch to iscsi system earlier:
https://patchwork.kernel.org/project/linux-scsi/patch/20221109092421.3111613-1-yangyingliang@huawei.com/
Mike give his point in the mail, so I send a new patch keep iscsi
maintainers Cced.
Thanks,
Yang
>
> thanks,
>
> greg k-h
>
> .
next prev parent reply other threads:[~2022-11-10 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 3:48 [PATCH] drivers: base: transport_class: fix possible memory leak Yang Yingliang
2022-11-10 8:18 ` Greg KH
2022-11-10 8:44 ` Yang Yingliang [this message]
2022-11-10 9:18 ` Greg KH
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=d509e930-779b-866e-9b1f-d58db6abfc43@huawei.com \
--to=yangyingliang@huawei.com \
--cc=cleech@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.ibm.com \
--cc=lduncan@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=open-iscsi@googlegroups.com \
--cc=rafael@kernel.org \
/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