From: Damien Le Moal <dlemoal@kernel.org>
To: Yu Kuai <yukuai1@huaweicloud.com>,
Zheng Qixing <zhengqixing@huawei.com>,
cassel@kernel.org
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, yangerkun@huawei.com,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH -next] ata: libata: Fix memory leak for error path in ata_host_alloc()
Date: Fri, 16 Aug 2024 19:32:34 +0900 [thread overview]
Message-ID: <5949965e-0155-4ad1-a019-df220140b085@kernel.org> (raw)
In-Reply-To: <3dfa5352-01d3-dc16-5a75-0b38e5893246@huaweicloud.com>
On 8/16/24 15:42, Yu Kuai wrote:
> 在 2024/08/16 11:58, Zheng Qixing 写道:
>> In ata_host_alloc(), if ata_port_alloc(host) fails to allocate memory
>> for a port, the allocated 'host' structure is not freed before returning
>> from the function. This results in a potential memory leak.
>>
>> This patch adds a kfree(host) before the error handling code is executed
>> to ensure that the 'host' structure is properly freed in case of an
>> allocation failure.
>>
>> Signed-off-by: Zheng Qixing <zhengqixing@huawei.com>
I did not receive this patch and I do not see it on the list either. Something
went wrong...
Can you resend please ? Thanks.
>> ---
>> drivers/ata/libata-core.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
>> index e4023fc288ac..f27a18990c38 100644
>> --- a/drivers/ata/libata-core.c
>> +++ b/drivers/ata/libata-core.c
>> @@ -5663,8 +5663,10 @@ struct ata_host *ata_host_alloc(struct device *dev, int n_ports)
>> }
>>
>> dr = devres_alloc(ata_devres_release, 0, GFP_KERNEL);
>> - if (!dr)
>> + if (!dr) {
>> + kfree(host);
>> goto err_out;
>> + }
>
> Looks correct, dev_set_drvdata(dev, host) is not called yet.
> ata_devres_release won't free host in this case.
>
> I'll suggest to return NULL directly here, and then the 'err_out'
> tag can be removed as well.
I do not think so. Since devres_open_group() was called, need to call either
devres_remove_group() or devres_release_group().
>
> Anyway, with or without the cleanup:
> Reviewed-by: Yu Kuai <yukuai3@huawei.com>>
> Thanks!
>>
>> devres_add(dev, dr);
>> dev_set_drvdata(dev, host);
>>
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-08-16 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240816035820.2055747-1-zhengqixing@huawei.com>
2024-08-16 6:42 ` Yu Kuai
2024-08-16 10:32 ` Damien Le Moal [this message]
2024-08-19 1:17 ` Yu Kuai
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=5949965e-0155-4ad1-a019-df220140b085@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.com \
--cc=zhengqixing@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®