From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: Wentao Liang <vulab@iscas.ac.cn>, airlied@gmail.com
Cc: alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org,
christian.koenig@amd.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, simona@ffwll.ch,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: Fix acpi device leak in amdgpu_acpi_enumerate_xcc()
Date: Wed, 16 Sep 2026 16:48:53 +0530 [thread overview]
Message-ID: <931daaa1-5c90-42ea-ad86-20ee22130851@amd.com> (raw)
In-Reply-To: <20260916095432.2009976-1-vulab@iscas.ac.cn>
On 16-Sep-26 3:24 PM, Wentao Liang wrote:
> amdgpu_acpi_enumerate_xcc() looks up each XCC ACPI device with
> acpi_dev_get_first_match_dev(), which takes a reference to the device.
> The reference is dropped with acpi_dev_put() after the XCC info is
> initialized, but if the kzalloc_obj() allocation of the XCC info fails
> the function returns -ENOMEM without releasing the reference, leaking
> the last reference to the ACPI device.
>
> Drop the ACPI device reference on the allocation failure path before
> returning.
>
> Fixes: 4d5275ab0b18 ("drm/amdgpu: Add parsing of acpi xcc objects")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
Reviewed-by: Lijo Lazar <lijo.lazar@amd.com>
Thanks,
Lijo
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c
> index 516ab9cf88fc..8d3f1f5a141e 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c
> @@ -1167,8 +1167,10 @@ int amdgpu_acpi_enumerate_xcc(void)
> }
>
> xcc_info = kzalloc_obj(struct amdgpu_acpi_xcc_info);
> - if (!xcc_info)
> + if (!xcc_info) {
> + acpi_dev_put(acpi_dev);
> return -ENOMEM;
> + }
>
> INIT_LIST_HEAD(&xcc_info->list);
> xcc_info->handle = acpi_device_handle(acpi_dev);
next prev parent reply other threads:[~2026-09-16 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 9:54 Wentao Liang
2026-09-16 11:18 ` Lazar, Lijo [this message]
2026-09-16 14:28 ` Deucher, Alexander
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=931daaa1-5c90-42ea-ad86-20ee22130851@amd.com \
--to=lijo.lazar@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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®