From: Alessio Belle <Alessio.Belle@imgtec.com>
To: "zhengxingda@iscas.ac.cn" <zhengxingda@iscas.ac.cn>
Cc: "airlied@gmail.com" <airlied@gmail.com>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"matt.coster@imgtec.com" <matt.coster@imgtec.com>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"uwu@icenowy.me" <uwu@icenowy.me>,
Brendan King <Brendan.King@imgtec.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frank Binns <Frank.Binns@imgtec.com>,
Brajesh Gupta <Brajesh.Gupta@imgtec.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"dakr@kernel.org" <dakr@kernel.org>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"mripard@kernel.org" <mripard@kernel.org>
Subject: Re: [PATCH v2] drm/imagination: acquire vm_ctx->lock before mapping memory to GPU VM
Date: Fri, 17 Jul 2026 11:14:52 +0000 [thread overview]
Message-ID: <164ad51d357350cde4e9e84cbe1ebc970c871af7.camel@imgtec.com> (raw)
In-Reply-To: <20260714073641.1935075-1-zhengxingda@iscas.ac.cn>
On Tue, 2026-07-14 at 15:36 +0800, Icenowy Zheng wrote:
> The drm gpuvm code doesn't protect find operation against map operation,
> and the driver needs to ensure a map operation shouldn't happen when a
> find operation is in progress.
>
> In some cases a find operation will be in progress when doing map/unmap
> operations, and the find operation will do a NULL pointer deference.
>
> An example of the stack trace of such NULL deference is shown below:
>
> ```
> Unable to handle kernel access to user memory without uaccess routines at
> virtual address 0000000000000010
>
> [<ffffffff01e989d4>] drm_gpuva_find+0x28/0x6c [drm_gpuvm]
> [<ffffffff01ed3a40>] pvr_vm_unmap+0x34/0x68 [powervr]
> [<ffffffff01ec69da>] pvr_ioctl_vm_unmap+0x2e/0x50 [powervr]
> [<ffffffff8080ce0a>] drm_ioctl_kernel+0x8e/0xdc
> [<ffffffff8080d016>] drm_ioctl+0x1be/0x3e0
> [<ffffffff802bec3e>] __riscv_sys_ioctl+0xba/0xc4
> [<ffffffff80d858b2>] do_trap_ecall_u+0x23e/0x3f4
> [<ffffffff80d92288>] handle_exception+0x168/0x174
> ```
>
> As all occurences of drm_gpuva_find*() are already guarded by
> vm_ctx->lock, make pvr_vm_map() to acquire this lock to prevent
> disturbing any find operation. This fixes the NULL deference problem in
> drm_gpuva_find*().
>
> Cc: stable@vger.kernel.org
> Fixes: ff5f643de0bf ("drm/imagination: Add GEM and VM related code")
> Fixes: 4bc736f890ce ("drm/imagination: vm: make use of GPUVM's drm_exec helper")
> Signed-off-by: Icenowy Zheng <zhengxingda@iscas.ac.cn>
Reviewed-by: Alessio Belle <alessio.belle@imgtec.com>
p.s. there's a double typo deference -> dereference that I can fix before
applying this early next week.
Thanks,
Alessio
> ---
> Changes in v2:
> - Dropped wrongly duplicated mutex_unlock() call and reordered it to
> before pvr_vm_bind_op_fini() (the lock is acquired after
> pvr_vm_bind_op_map_init() call). (Thanks to Brajesh)
> - Added a extra Fixes pointing to the original broken code that was
> refactored by the original Fixes (but still broken). (Thanks to
> Alessio)
> - Fixed some typos in commit message. (Thanks to Alessio)
> - Added a stacktrace of the oops that occured on my board. (As suggested
> by Alessio)
>
> drivers/gpu/drm/imagination/pvr_vm.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/imagination/pvr_vm.c b/drivers/gpu/drm/imagination/pvr_vm.c
> index 396d349fb6ce4..ceb78694cd987 100644
> --- a/drivers/gpu/drm/imagination/pvr_vm.c
> +++ b/drivers/gpu/drm/imagination/pvr_vm.c
> @@ -747,6 +747,7 @@ pvr_vm_map(struct pvr_vm_context *vm_ctx, struct pvr_gem_object *pvr_obj,
>
> pvr_gem_object_get(pvr_obj);
>
> + mutex_lock(&vm_ctx->lock);
> err = drm_gpuvm_exec_lock(&vm_exec);
> if (err)
> goto err_cleanup;
> @@ -756,6 +757,7 @@ pvr_vm_map(struct pvr_vm_context *vm_ctx, struct pvr_gem_object *pvr_obj,
> drm_gpuvm_exec_unlock(&vm_exec);
>
> err_cleanup:
> + mutex_unlock(&vm_ctx->lock);
> pvr_vm_bind_op_fini(&bind_op);
>
> return err;
next prev parent reply other threads:[~2026-07-17 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 7:36 Icenowy Zheng
2026-07-17 11:14 ` Alessio Belle [this message]
2026-07-17 17:06 ` Icenowy Zheng
-- strict thread matches above, loose matches on Subject: below --
2026-04-21 17:57 Icenowy Zheng
2026-07-06 14:22 ` Brajesh Gupta
2026-07-13 17:07 ` Alessio Belle
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=164ad51d357350cde4e9e84cbe1ebc970c871af7.camel@imgtec.com \
--to=alessio.belle@imgtec.com \
--cc=Brajesh.Gupta@imgtec.com \
--cc=Brendan.King@imgtec.com \
--cc=Frank.Binns@imgtec.com \
--cc=airlied@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matt.coster@imgtec.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
--cc=uwu@icenowy.me \
--cc=zhengxingda@iscas.ac.cn \
/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