From: Li Tuo <islituo@gmail.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, airlied@linux.ie,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
Xinhui.Pan@amd.com, baijiaju1990@gmail.com,
alexander.deucher@amd.com, Philip.Yang@amd.com,
TOTE Robot <oslab@tsinghua.edu.cn>,
sumit.semwal@linaro.org, daniel@ffwll.ch, Felix.Kuehling@amd.com,
airlied@redhat.com, Oak.Zeng@amd.com, nirmoy.das@amd.com,
tzimmermann@suse.de
Subject: Re: [PATCH] drm/amdgpu: fix possible null-pointer dereference in amdgpu_ttm_tt_populate()
Date: Mon, 2 Aug 2021 10:47:24 +0800 [thread overview]
Message-ID: <fc060208-89b5-51aa-c956-adf7c42d6b79@gmail.com> (raw)
In-Reply-To: <53ef6ff7-f793-5de4-4ab4-0efbfbfc0a54@amd.com>
Thanks for your feedback! We will remove the null tests according to
your advice and prepare a V2 patch.
Best wishes,
Tuo Li
On 2021/8/2 1:19, Christian König wrote:
> Am 31.07.21 um 10:04 schrieb Tuo Li:
>> The variable ttm is assigned to the variable gtt, and the variable gtt
>> is checked in:
>> if (gtt && gtt->userptr)
>>
>> This indicates that both ttm and gtt can be NULL.
>> If so, a null-pointer dereference will occur:
>> if (ttm->page_flags & TTM_PAGE_FLAG_SG)
>>
>> Also, some null-pointer dereferences will occur in the function
>> ttm_pool_alloc() which is called in:
>> return ttm_pool_alloc(&adev->mman.bdev.pool, ttm, ctx);
>>
>> To fix these possible null-pointer dereferences, the function returns
>> -EINVAL when ttm is NULL.
>
> NAK, the NULL test is just a leftover from when the objects where
> distinct.
>
> Please remove the NULL test instead.
>
> Regards,
> Christian.
>
>>
>> Reported-by: TOTE Robot <oslab@tsinghua.edu.cn>
>> Signed-off-by: Tuo Li <islituo@gmail.com>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
>> index 3a55f08e00e1..80440f799c09 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
>> @@ -1120,8 +1120,11 @@ static int amdgpu_ttm_tt_populate(struct
>> ttm_device *bdev,
>> struct amdgpu_device *adev = amdgpu_ttm_adev(bdev);
>> struct amdgpu_ttm_tt *gtt = (void *)ttm;
>> + if (ttm == NULL)
>> + return -EINVAL;
>> +
>> /* user pages are bound by amdgpu_ttm_tt_pin_userptr() */
>> - if (gtt && gtt->userptr) {
>> + if (gtt->userptr) {
>> ttm->sg = kzalloc(sizeof(struct sg_table), GFP_KERNEL);
>> if (!ttm->sg)
>> return -ENOMEM;
>
prev parent reply other threads:[~2021-08-02 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 8:04 Tuo Li
2021-08-01 17:19 ` Christian König
2021-08-02 2:47 ` Li Tuo [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=fc060208-89b5-51aa-c956-adf7c42d6b79@gmail.com \
--to=islituo@gmail.com \
--cc=Felix.Kuehling@amd.com \
--cc=Oak.Zeng@amd.com \
--cc=Philip.Yang@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=baijiaju1990@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=nirmoy.das@amd.com \
--cc=oslab@tsinghua.edu.cn \
--cc=sumit.semwal@linaro.org \
--cc=tzimmermann@suse.de \
/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®