From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: "Guangshuo Li" <lgs201920130244@gmail.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Hawking Zhang" <Hawking.Zhang@amd.com>,
"Likun Gao" <Likun.Gao@amd.com>,
"Asad Kamal" <asad.kamal@amd.com>, "Ce Sun" <cesun102@amd.com>,
"Kees Cook" <kees@kernel.org>, "Meng Li" <li.meng@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: Fix error handling in amdgpu_xcp_cfg_sysfs_init()
Date: Tue, 28 Apr 2026 17:40:50 +0530 [thread overview]
Message-ID: <a5bbcbeb-b2a2-442c-b2df-7dbfef8bf442@amd.com> (raw)
In-Reply-To: <20260428114521.364863-1-lgs201920130244@gmail.com>
On 28-Apr-26 5:15 PM, Guangshuo Li wrote:
> [You don't often get email from lgs201920130244@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Once kobject_init_and_add() fails for an XCP resource kobject, we
> should call kobject_put() to decrement the reference count for cleanup.
> Otherwise, it could cause a memory leak.
>
> The error handling loop also uses xcp_res[i] instead of xcp_res[j],
> so it fails to put the previously added resource kobjects and may put
> the failed kobject more than once.
>
> Fix this by putting the failed resource kobject before jumping to the
> error path, and by using the correct loop index when putting the
> previously added resource kobjects.
>
> Found by code review.
>
> Fixes: 4ae86dc87850 ("drm/amdgpu: Add sysfs nodes to get xcp details")
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_xcp.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_xcp.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_xcp.c
> index cc5f4e01e38f..315e33a9d7c9 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_xcp.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_xcp.c
> @@ -948,15 +948,17 @@ static void amdgpu_xcp_cfg_sysfs_init(struct amdgpu_device *adev)
> &xcp_cfg_res_sysfs_ktype,
> &xcp_cfg->kobj, "%s",
> xcp_res_names[rid]);
> - if (r)
> + if (r) {
> + kobject_put(&xcp_res->kobj);
> goto err;
> + }
> }
>
> adev->xcp_mgr->xcp_cfg = xcp_cfg;
> return;
> err:
> for (j = 0; j < i; j++) {
> - xcp_res = &xcp_cfg->xcp_res[i];
> + xcp_res = &xcp_cfg->xcp_res[j];
Good catch. What about just keeping it j <= i? Seeing only one path to
get to this error handling.
Thanks,
Lijo
> kobject_put(&xcp_res->kobj);
> }
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-04-28 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 11:45 [PATCH] drm/amdgpu: Fix error handling in amdgpu_xcp_cfg_sysfs_init() Guangshuo Li
2026-04-28 12:10 ` Lazar, Lijo [this message]
2026-04-28 12:39 ` Christian König
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=a5bbcbeb-b2a2-442c-b2df-7dbfef8bf442@amd.com \
--to=lijo.lazar@amd.com \
--cc=Hawking.Zhang@amd.com \
--cc=Likun.Gao@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=asad.kamal@amd.com \
--cc=cesun102@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kees@kernel.org \
--cc=lgs201920130244@gmail.com \
--cc=li.meng@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
/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