public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: Li Huafei <lihuafei1@huawei.com>, alexander.deucher@amd.com
Cc: christian.koenig@amd.com, Xinhui.Pan@amd.com, airlied@gmail.com,
	simona@ffwll.ch, Hawking.Zhang@amd.com, yifan1.zhang@amd.com,
	Likun.Gao@amd.com, Tim.Huang@amd.com, pratap.nirujogi@amd.com,
	victorchengchi.lu@amd.com, Jun.Ma2@amd.com, le.ma@amd.com,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: Fix possible NULL pointer dereference
Date: Mon, 28 Oct 2024 20:03:31 +0530	[thread overview]
Message-ID: <de0e660b-395f-4a26-8bbc-199df83a90b4@amd.com> (raw)
In-Reply-To: <20241028215933.2599271-1-lihuafei1@huawei.com>



On 10/29/2024 3:29 AM, Li Huafei wrote:
> Fix the potential NULL pointer dereference on mem_ranges in
> amdgpu_discovery_get_nps_info(). Additionally, assign the output
> parameters nps_type and range_cnt after the kvzalloc() call to prevent
> modifying the output parameters in case of an error return.
> 
> Fixes: b194d21b9bcc ("drm/amdgpu: Use NPS ranges from discovery table")
> Signed-off-by: Li Huafei <lihuafei1@huawei.com>
> ---
>  drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c
> index 4bd61c169ca8..1b1aedebb3c2 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c
> @@ -1757,11 +1757,13 @@ int amdgpu_discovery_get_nps_info(struct amdgpu_device *adev,
>  
>  	switch (le16_to_cpu(nps_info->v1.header.version_major)) {
>  	case 1:
> -		*nps_type = nps_info->v1.nps_type;
> -		*range_cnt = nps_info->v1.count;

This one is used in the allocation call below. If you prefer to not
assign any of the out params before memory allocation is successful,
then use nps_info->v1.count in the alloc call.

Thanks for adding the alloc fail check.

Thanks,
Lijo
>  		mem_ranges = kvzalloc(
>  			*range_cnt * sizeof(struct amdgpu_gmc_memrange),
>  			GFP_KERNEL);
> +		if (!mem_ranges)
> +			return -ENOMEM;
> +		*nps_type = nps_info->v1.nps_type;
> +		*range_cnt = nps_info->v1.count;
>  		for (i = 0; i < *range_cnt; i++) {
>  			mem_ranges[i].base_address =
>  				nps_info->v1.instance_info[i].base_address;

  reply	other threads:[~2024-10-28 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 21:59 [PATCH] drm/amdgpu: Fix possible NULL pointer dereference Li Huafei
2024-10-28 14:33 ` Lazar, Lijo [this message]
2024-10-29  1:17   ` Li Huafei

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=de0e660b-395f-4a26-8bbc-199df83a90b4@amd.com \
    --to=lijo.lazar@amd.com \
    --cc=Hawking.Zhang@amd.com \
    --cc=Jun.Ma2@amd.com \
    --cc=Likun.Gao@amd.com \
    --cc=Tim.Huang@amd.com \
    --cc=Xinhui.Pan@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=le.ma@amd.com \
    --cc=lihuafei1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pratap.nirujogi@amd.com \
    --cc=simona@ffwll.ch \
    --cc=victorchengchi.lu@amd.com \
    --cc=yifan1.zhang@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