AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Ruijing Dong <ruijing.dong@amd.com>,
	Alexander.Deucher@amd.com, amd-gfx@lists.freedesktop.org
Cc: leo.liu@amd.com
Subject: Re: [PATCH] drm/amdgpu: fix strsep() corrupting lockup_timeout module parameter on multi-GPU
Date: Wed, 18 Mar 2026 08:30:52 +0100	[thread overview]
Message-ID: <70c5a048-7dfc-4024-8031-aae0d7b4dfb3@amd.com> (raw)
In-Reply-To: <20260317181759.34331-1-ruijing.dong@amd.com>

On 3/17/26 19:17, Ruijing Dong wrote:
> amdgpu_device_get_job_timeout_settings() passes a pointer directly to
> the global amdgpu_lockup_timeout[] buffer into strsep(). strsep()
> destructively replaces delimiter characters with '\0' in-place.
> 
> On multi-GPU systems, this function is called once per device. When a
> multi-value setting like "0,0,0,-1" is used, the first GPU's call
> transforms the global buffer into "0\00\00\0-1". The second GPU then
> sees only "0" (terminated at the first '\0'), parses a single value,
> hits the single-value fallthrough (index == 1), and applies timeout=0
> to all rings — causing immediate false job timeouts.
> 
> Fix this by using kstrdup() to make a local copy before calling strsep(),
> so the global module parameter buffer remains intact across calls. A
> separate pointer is kept to the allocation start since strsep() advances
> the working pointer to NULL by the end of parsing.
> 
> Signed-off-by: Ruijing Dong <ruijing.dong@amd.com>
> ---
>  drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 19 ++++++++++++++++---
>  1 file changed, 16 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> index dcae77b6c272..97ebcc5bb763 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> @@ -3498,7 +3498,7 @@ static void amdgpu_device_xgmi_reset_func(struct work_struct *__work)
>  
>  static int amdgpu_device_get_job_timeout_settings(struct amdgpu_device *adev)
>  {
> -	char *input = amdgpu_lockup_timeout;
> +	char *input, *input_copy;
>  	char *timeout_setting = NULL;
>  	int index = 0;
>  	long timeout;
> @@ -3508,14 +3508,25 @@ static int amdgpu_device_get_job_timeout_settings(struct amdgpu_device *adev)
>  	adev->gfx_timeout = adev->compute_timeout = adev->sdma_timeout =
>  		adev->video_timeout = msecs_to_jiffies(2000);
>  
> -	if (!strnlen(input, AMDGPU_MAX_TIMEOUT_PARAM_LENGTH))
> +	if (!strnlen(amdgpu_lockup_timeout, AMDGPU_MAX_TIMEOUT_PARAM_LENGTH))
>  		return 0;
>  
> +	/*
> +	 * strsep() destructively modifies its input by replacing delimiters
> +	 * with '\0'. Make a local copy so the global module parameter buffer
> +	 * remains intact for multi-GPU systems where this function is called
> +	 * once per device.
> +	 */
> +	input = kstrdup(amdgpu_lockup_timeout, GFP_KERNEL);

I think it is save to copy the parameter to the stack instead of using kmalloc() here.

Apart from that it's a pretty good catch.

Regards,
Christian.

> +	if (!input)
> +		return -ENOMEM;
> +	input_copy = input;
> +
>  	while ((timeout_setting = strsep(&input, ",")) &&
>  	       strnlen(timeout_setting, AMDGPU_MAX_TIMEOUT_PARAM_LENGTH)) {
>  		ret = kstrtol(timeout_setting, 0, &timeout);
>  		if (ret)
> -			return ret;
> +			goto out_free;
>  
>  		if (timeout == 0) {
>  			index++;
> @@ -3551,6 +3562,8 @@ static int amdgpu_device_get_job_timeout_settings(struct amdgpu_device *adev)
>  		adev->gfx_timeout = adev->compute_timeout = adev->sdma_timeout =
>  			adev->video_timeout = timeout;
>  
> +out_free:
> +	kfree(input_copy);
>  	return ret;
>  }
>  


      reply	other threads:[~2026-03-18  7:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 18:17 [PATCH] drm/amdgpu: fix strsep() corrupting lockup_timeout module parameter on multi-GPU Ruijing Dong
2026-03-18  7:30 ` Christian König [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=70c5a048-7dfc-4024-8031-aae0d7b4dfb3@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=leo.liu@amd.com \
    --cc=ruijing.dong@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