The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Zheyu Ma <zheyuma97@gmail.com>,
	ray.huang@amd.com, airlied@linux.ie, daniel@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/ttm: add a check against null pointer dereference
Date: Wed, 14 Jul 2021 17:06:34 +0200	[thread overview]
Message-ID: <e3232983-895d-b24c-2e25-bf874d8007b1@amd.com> (raw)
In-Reply-To: <1626274459-8148-1-git-send-email-zheyuma97@gmail.com>

Am 14.07.21 um 16:54 schrieb Zheyu Ma:
> When calling ttm_range_man_fini(), 'man' may be uninitialized, which may
> cause a null pointer dereference bug.
>
> Fix this by checking if it is a null pointer.

It would be better if the driver doesn't try to fini a manager which was 
never initialized, but for now that should work.

>
> This log reveals it:
>
> [    7.902580 ] BUG: kernel NULL pointer dereference, address: 0000000000000058
> [    7.905721 ] RIP: 0010:ttm_range_man_fini+0x40/0x160
> [    7.911826 ] Call Trace:
> [    7.911826 ]  radeon_ttm_fini+0x167/0x210
> [    7.911826 ]  radeon_bo_fini+0x15/0x40
> [    7.913767 ]  rs400_fini+0x55/0x80
> [    7.914358 ]  radeon_device_fini+0x3c/0x140
> [    7.914358 ]  radeon_driver_unload_kms+0x5c/0xe0
> [    7.914358 ]  radeon_driver_load_kms+0x13a/0x200
> [    7.914358 ]  ? radeon_driver_unload_kms+0xe0/0xe0
> [    7.914358 ]  drm_dev_register+0x1db/0x290
> [    7.914358 ]  radeon_pci_probe+0x16a/0x230
> [    7.914358 ]  local_pci_probe+0x4a/0xb0
>
> Signed-off-by: Zheyu Ma <zheyuma97@gmail.com>

Reviewed-by: Christian König <christian.koenig@amd.com>

Going to push it later.

Thanks,
Christian.

> ---
>   drivers/gpu/drm/ttm/ttm_range_manager.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/ttm/ttm_range_manager.c b/drivers/gpu/drm/ttm/ttm_range_manager.c
> index 03395386e8a7..f4b08a8705b3 100644
> --- a/drivers/gpu/drm/ttm/ttm_range_manager.c
> +++ b/drivers/gpu/drm/ttm/ttm_range_manager.c
> @@ -181,6 +181,9 @@ int ttm_range_man_fini(struct ttm_device *bdev,
>   	struct drm_mm *mm = &rman->mm;
>   	int ret;
>   
> +	if (!man)
> +		return 0;
> +
>   	ttm_resource_manager_set_used(man, false);
>   
>   	ret = ttm_resource_manager_evict_all(bdev, man);


      reply	other threads:[~2021-07-14 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 14:54 [PATCH] drm/ttm: add a check against null pointer dereference Zheyu Ma
2021-07-14 15:06 ` 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=e3232983-895d-b24c-2e25-bf874d8007b1@amd.com \
    --to=christian.koenig@amd.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray.huang@amd.com \
    --cc=zheyuma97@gmail.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