From: Li Huafei <lihuafei1@huawei.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
<alexander.deucher@amd.com>, <lijo.lazar@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 v2] drm/amdgpu: Fix possible NULL pointer dereference
Date: Tue, 29 Oct 2024 20:36:16 +0800 [thread overview]
Message-ID: <44f29433-1fe7-7d6d-616b-3f6755d2f9f3@huawei.com> (raw)
In-Reply-To: <2a070669-aa48-413e-959c-4107d9c2f97c@wanadoo.fr>
On 2024/10/29 16:18, Christophe JAILLET wrote:
> Le 29/10/2024 à 11:18, Li Huafei a écrit :
>> 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>
>> ---
>> Changes in v2:
>> - kvzalloc() call uses 'nps_info->v1.count' instead of '*range_cnt'
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c
>> index 4bd61c169ca8..9a0b1b208a9d 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;
>> mem_ranges = kvzalloc(
>
> Not strictly related to your fix, but this could also be kvcalloc() to
> avoid potential overflow in the multiplication.
>
Good suggestion! I added this modification in v3:
v3: https://lore.kernel.org/lkml/20241029202758.2764535-1-lihuafei1@huawei.com/T/#u
Lijo, I've added your Reviewed-by tag in v3. If you have any questions about the kvcalloc() modification, please let me know.
Thanks,
Huafei
> CJ
>
>> - *range_cnt * sizeof(struct amdgpu_gmc_memrange),
>> + nps_info->v1.count * 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;
>
>
> .
prev parent reply other threads:[~2024-10-29 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 10:18 Li Huafei
2024-10-29 4:04 ` Lazar, Lijo
2024-10-29 8:18 ` Christophe JAILLET
2024-10-29 12:36 ` Li Huafei [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=44f29433-1fe7-7d6d-616b-3f6755d2f9f3@huawei.com \
--to=lihuafei1@huawei.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=christophe.jaillet@wanadoo.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=le.ma@amd.com \
--cc=lijo.lazar@amd.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
all inboxes | Powered by JetHome®