From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Ma Ke <make24@iscas.ac.cn>
Cc: sumit.garg@linaro.org, gregkh@linuxfoundation.org,
elder@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v4] [ARM] fix reference leak in locomo_init_one_child()
Date: Mon, 13 Jan 2025 12:45:35 +0000 [thread overview]
Message-ID: <Z4UK7__tlAZrucRd@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250108033049.1206055-1-make24@iscas.ac.cn>
On Wed, Jan 08, 2025 at 11:30:49AM +0800, Ma Ke wrote:
> Once device_register() failed, we should call put_device() to
> decrement reference count for cleanup. Or it could cause memory leak.
>
> device_register() includes device_add(). As comment of device_add()
> says, 'if device_add() succeeds, you should call device_del() when you
> want to get rid of it. If device_add() has not succeeded, use only
> put_device() to drop the reference count'.
I reviewed a previous version of this patch, and commented about the
commit message:
The commit message is not quite correct:
"After calling device_register(), the correct way to dispose of the
device is to call put_device() as per the device_register()
documentation rather than kfree()."
Alex Elder also commented about this. Please fix the commit message.
What device_add() doesn't matter, this code isn't calling device_add(),
it's calling device_register(), and the comments against
device_register() should be appearing in the commit message, not
the comments against device_add().
Thanks.
>
> Found by code review.
>
> Cc: stable@vger.kernel.org
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Ma Ke <make24@iscas.ac.cn>
> ---
> Changes in v4:
> - deleted the redundant initialization;
> Changes in v3:
> - modified the patch as suggestions;
> Changes in v2:
> - modified the patch as suggestions.
> ---
> arch/arm/common/locomo.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/arch/arm/common/locomo.c b/arch/arm/common/locomo.c
> index cb6ef449b987..45106066a17f 100644
> --- a/arch/arm/common/locomo.c
> +++ b/arch/arm/common/locomo.c
> @@ -223,10 +223,8 @@ locomo_init_one_child(struct locomo *lchip, struct locomo_dev_info *info)
> int ret;
>
> dev = kzalloc(sizeof(struct locomo_dev), GFP_KERNEL);
> - if (!dev) {
> - ret = -ENOMEM;
> - goto out;
> - }
> + if (!dev)
> + return -ENOMEM;
>
> /*
> * If the parent device has a DMA mask associated with it,
> @@ -254,10 +252,9 @@ locomo_init_one_child(struct locomo *lchip, struct locomo_dev_info *info)
> NO_IRQ : lchip->irq_base + info->irq[0];
>
> ret = device_register(&dev->dev);
> - if (ret) {
> - out:
> - kfree(dev);
> - }
> + if (ret)
> + put_device(&dev->dev);
> +
> return ret;
> }
>
> --
> 2.25.1
>
>
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2025-01-13 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 3:30 [PATCH v4] [ARM] fix reference leak in locomo_init_one_child() Ma Ke
2025-01-09 3:06 ` Alex Elder
2025-01-13 12:45 ` Russell King (Oracle) [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=Z4UK7__tlAZrucRd@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=make24@iscas.ac.cn \
--cc=stable@vger.kernel.org \
--cc=sumit.garg@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.