mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Ma Ke <make24@iscas.ac.cn>,
	linux@armlinux.org.uk, thierry.reding@gmail.com,
	johan@kernel.org, hdoyu@nvidia.com, swarren@nvidia.com
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, stable@vger.kernel.org
Subject: Re: [PATCH RESEND] ARM: tegra: fix device leak on tegra ahb lookup
Date: Mon, 15 Dec 2025 20:03:10 +0000	[thread overview]
Message-ID: <64761b5c-1dc4-43da-a348-3db994ca5e87@nvidia.com> (raw)
In-Reply-To: <20251214125317.2086-1-make24@iscas.ac.cn>


On 14/12/2025 12:53, Ma Ke wrote:
> tegra_ahb_enable_smmu() utilizes driver_find_device_by_of_node() which
> internally calls driver_find_device() to locate the matching device.
> driver_find_device() increments the ref count of the found device by
> calling get_device(), but tegra_ahb_enable_smmu() fails to call
> put_device() to decrement the reference count before returning. This
> results in a reference count leak of the device, which may prevent the
> device from being properly released and cause a memory leak.
> 
> Found by code review.
> 
> Cc: stable@vger.kernel.org
> Fixes: 89c788bab1f0 ("ARM: tegra: Add SMMU enabler in AHB")
> Signed-off-by: Ma Ke <make24@iscas.ac.cn>
> ---
>   drivers/amba/tegra-ahb.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/amba/tegra-ahb.c b/drivers/amba/tegra-ahb.c
> index f23c3ed01810..3ed5cef34806 100644
> --- a/drivers/amba/tegra-ahb.c
> +++ b/drivers/amba/tegra-ahb.c
> @@ -148,6 +148,7 @@ int tegra_ahb_enable_smmu(struct device_node *dn)
>   	val = gizmo_readl(ahb, AHB_ARBITRATION_XBAR_CTRL);
>   	val |= AHB_ARBITRATION_XBAR_CTRL_SMMU_INIT_DONE;
>   	gizmo_writel(ahb, val, AHB_ARBITRATION_XBAR_CTRL);
> +	put_device(dev);
>   	return 0;
>   }
>   EXPORT_SYMBOL(tegra_ahb_enable_smmu);


This has already been fixed and so this change is not needed.

-- 
nvpublic


      reply	other threads:[~2025-12-15 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-14 12:53 Ma Ke
2025-12-15 20:03 ` Jon Hunter [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=64761b5c-1dc4-43da-a348-3db994ca5e87@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=hdoyu@nvidia.com \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=make24@iscas.ac.cn \
    --cc=stable@vger.kernel.org \
    --cc=swarren@nvidia.com \
    --cc=thierry.reding@gmail.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®