From: "Christian König" <christian.koenig@amd.com>
To: Tong Zhang <ztong0001@gmail.com>,
Alex Deucher <alexander.deucher@amd.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/radeon: don't evict if not initialized
Date: Sun, 21 Mar 2021 14:26:27 +0100 [thread overview]
Message-ID: <d50c08e5-51d7-148c-464f-7699e6f6a115@amd.com> (raw)
In-Reply-To: <20210320201052.114775-1-ztong0001@gmail.com>
Am 20.03.21 um 21:10 schrieb Tong Zhang:
> TTM_PL_VRAM may not initialized at all when calling
> radeon_bo_evict_vram(). We need to check before doing eviction.
>
> [ 2.160837] BUG: kernel NULL pointer dereference, address: 0000000000000020
> [ 2.161212] #PF: supervisor read access in kernel mode
> [ 2.161490] #PF: error_code(0x0000) - not-present page
> [ 2.161767] PGD 0 P4D 0
> [ 2.163088] RIP: 0010:ttm_resource_manager_evict_all+0x70/0x1c0 [ttm]
> [ 2.168506] Call Trace:
> [ 2.168641] radeon_bo_evict_vram+0x1c/0x20 [radeon]
> [ 2.168936] radeon_device_fini+0x28/0xf9 [radeon]
> [ 2.169224] radeon_driver_unload_kms+0x44/0xa0 [radeon]
> [ 2.169534] radeon_driver_load_kms+0x174/0x210 [radeon]
> [ 2.169843] drm_dev_register+0xd9/0x1c0 [drm]
> [ 2.170104] radeon_pci_probe+0x117/0x1a0 [radeon]
>
> Signed-off-by: Tong Zhang <ztong0001@gmail.com>
> ---
> drivers/gpu/drm/radeon/radeon_object.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_object.c b/drivers/gpu/drm/radeon/radeon_object.c
> index 9b81786782de..04e9a8118b0e 100644
> --- a/drivers/gpu/drm/radeon/radeon_object.c
> +++ b/drivers/gpu/drm/radeon/radeon_object.c
> @@ -384,7 +384,9 @@ int radeon_bo_evict_vram(struct radeon_device *rdev)
> }
> #endif
> man = ttm_manager_type(bdev, TTM_PL_VRAM);
> - return ttm_resource_manager_evict_all(bdev, man);
> + if (man)
> + return ttm_resource_manager_evict_all(bdev, man);
> + return 0;
You should probably code this the other way around, e.g.
If (!man)
return 0;
...
Apart from that looks good to me.
Christian.
> }
>
> void radeon_bo_force_delete(struct radeon_device *rdev)
next prev parent reply other threads:[~2021-03-21 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 20:10 Tong Zhang
2021-03-21 13:26 ` Christian König [this message]
2021-03-21 15:20 ` Tong Zhang
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=d50c08e5-51d7-148c-464f-7699e6f6a115@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ztong0001@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
all inboxes | Powered by JetHome®