From: "Christian König" <christian.koenig@amd.com>
To: Jiang Liu <gerry@linux.alibaba.com>,
alexander.deucher@amd.com, Xinhui.Pan@amd.com, airlied@gmail.com,
simona@ffwll.ch, sunil.khatri@amd.com, lijo.lazar@amd.com,
Hawking.Zhang@amd.com, mario.limonciello@amd.com,
xiaogang.chen@amd.com, Kent.Russell@amd.com,
shuox.liu@linux.alibaba.com, amd-gfx@lists.freedesktop.org
Subject: Re: [v5 5/5] drm/amdgpu: fix invalid memory access in amdgpu_fence_driver_sw_fini()
Date: Mon, 20 Jan 2025 10:04:32 +0100 [thread overview]
Message-ID: <5a5af585-cfa1-473f-a758-29e47b49ef50@amd.com> (raw)
In-Reply-To: <2e4357dd1daf3068b1b883be604a335cc2be8c3a.1737100293.git.gerry@linux.alibaba.com>
Am 17.01.25 um 08:55 schrieb Jiang Liu:
> Introduce amdgpu_device_fini_schedulers() to clean scheduler related
> resources, and avoid possible invalid memory access.
>
> Signed-off-by: Jiang Liu <gerry@linux.alibaba.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 35 +++++++++++++++++++---
> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 9 ------
> 2 files changed, 31 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> index ee695e70fb4f..dd94f87c1f7c 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> @@ -2821,6 +2821,26 @@ static int amdgpu_device_fw_loading(struct amdgpu_device *adev)
> return r;
> }
>
> +static void __amdgpu_device_fini_schedulers(struct amdgpu_device *adev,
> + int num_rings)
> +{
> + int i;
> +
> + for (i = 0; i < num_rings; ++i) {
> + struct amdgpu_ring *ring = adev->rings[i];
> +
> + if (!ring || ring->no_scheduler)
> + continue;
> +
> + drm_sched_fini(&ring->sched);
> + }
> +}
> +
> +static void amdgpu_device_fini_schedulers(struct amdgpu_device *adev)
> +{
> + __amdgpu_device_fini_schedulers(adev, AMDGPU_MAX_RINGS);
> +}
> +
> static int amdgpu_device_init_schedulers(struct amdgpu_device *adev)
> {
> long timeout;
> @@ -2857,27 +2877,32 @@ static int amdgpu_device_init_schedulers(struct amdgpu_device *adev)
> if (r) {
> DRM_ERROR("Failed to create scheduler on ring %s.\n",
> ring->name);
> - return r;
> + goto out_err;
> }
> r = amdgpu_uvd_entity_init(adev, ring);
> if (r) {
> DRM_ERROR("Failed to create UVD scheduling entity on ring %s.\n",
> ring->name);
> - return r;
> + goto out_sched_fini;
> }
> r = amdgpu_vce_entity_init(adev, ring);
> if (r) {
> DRM_ERROR("Failed to create VCE scheduling entity on ring %s.\n",
> ring->name);
> - return r;
> + goto out_sched_fini;
> }
> }
>
> amdgpu_xcp_update_partition_sched_list(adev);
>
> return 0;
> -}
>
> +out_sched_fini:
> + drm_sched_fini(&adev->rings[i]->sched);
> +out_err:
> + __amdgpu_device_fini_schedulers(adev, i);
I would just open code that as:
while (i--)
if (adev->rings[i] && !adev->rings[i]->no_scheduler)
drm_sched_fini(adev->rings[i]);
instead of delegating that to the __amdgpu_device_fini_schedulers()
function.
That makes code maintenance easier should anything more need to be added
to the amdgpu_device_fini_schedulers() function in the future.
Regards,
Christian.
> + return r;
> +}
>
> /**
> * amdgpu_device_ip_init - run init for hardware IPs
> @@ -3424,6 +3449,8 @@ static int amdgpu_device_ip_fini(struct amdgpu_device *adev)
>
> amdgpu_amdkfd_device_fini_sw(adev);
>
> + amdgpu_device_fini_schedulers(adev);
> +
> for (i = adev->num_ip_blocks - 1; i >= 0; i--) {
> if (!adev->ip_blocks[i].status.sw)
> continue;
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> index 2f24a6aa13bf..c95895a7b888 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> @@ -650,15 +650,6 @@ void amdgpu_fence_driver_sw_fini(struct amdgpu_device *adev)
> if (!ring || !ring->fence_drv.initialized)
> continue;
>
> - /*
> - * Notice we check for sched.ops since there's some
> - * override on the meaning of sched.ready by amdgpu.
> - * The natural check would be sched.ready, which is
> - * set as drm_sched_init() finishes...
> - */
> - if (ring->sched.ops)
> - drm_sched_fini(&ring->sched);
> -
> for (j = 0; j <= ring->fence_drv.num_fences_mask; ++j)
> dma_fence_put(ring->fence_drv.fences[j]);
> kfree(ring->fence_drv.fences);
next prev parent reply other threads:[~2025-01-20 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 7:55 [v5 0/5] Fix several bugs in error handling during device probe Jiang Liu
2025-01-17 7:55 ` [v5 1/5] drm/amdxcp: introduce new API amdgpu_xcp_drm_dev_free() Jiang Liu
2025-01-17 7:55 ` [v5 2/5] drm/amdgpu: fix use after free bug related to amdgpu_driver_release_kms() Jiang Liu
2025-01-17 7:55 ` [v5 3/5] drm/amdgpu: fix invalid memory access in amdgpu_xcp_cfg_sysfs_fini() Jiang Liu
2025-01-17 7:55 ` [v5 4/5] drm/amdgpu: enhance error handling in function amdgpu_pci_probe() Jiang Liu
2025-01-17 7:55 ` [v5 5/5] drm/amdgpu: fix invalid memory access in amdgpu_fence_driver_sw_fini() Jiang Liu
2025-01-20 9:04 ` Christian König [this message]
2025-01-24 3:04 ` Gerry Liu
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=5a5af585-cfa1-473f-a758-29e47b49ef50@amd.com \
--to=christian.koenig@amd.com \
--cc=Hawking.Zhang@amd.com \
--cc=Kent.Russell@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=gerry@linux.alibaba.com \
--cc=lijo.lazar@amd.com \
--cc=mario.limonciello@amd.com \
--cc=shuox.liu@linux.alibaba.com \
--cc=simona@ffwll.ch \
--cc=sunil.khatri@amd.com \
--cc=xiaogang.chen@amd.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