From: Donald Robson <Donald.Robson@imgtec.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>,
Frank Binns <Frank.Binns@imgtec.com>,
Matt Coster <Matt.Coster@imgtec.com>,
"mripard@kernel.org" <mripard@kernel.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"dakr@redhat.com" <dakr@redhat.com>,
Sarah Walker <Sarah.Walker@imgtec.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXTERNAL] [PATCH drm-misc-next 2/5] drm/imagination: vm: check for drm_gpuvm_range_valid()
Date: Tue, 28 Nov 2023 10:34:28 +0000 [thread overview]
Message-ID: <bcd3a9fb156c773ac942818213e6192fe36dc6ac.camel@imgtec.com> (raw)
In-Reply-To: <20231124233650.152653-3-dakr@redhat.com>
Thanks Danilo.
Reviewed-by: Donald Robson <donald.robson@imgtec.com>
On Sat, 2023-11-25 at 00:36 +0100, Danilo Krummrich wrote:
> *** CAUTION: This email originates from a source not known to Imagination Technologies. Think before you click a link or open an attachment ***
>
> Extend pvr_device_addr_and_size_are_valid() by the corresponding GPUVM
> sanity checks. This includes a, previously missing, overflow check for
> the base address and size of the requested mapping.
>
> Fixes: ff5f643de0bf ("drm/imagination: Add GEM and VM related code")
> Signed-off-by: Danilo Krummrich <dakr@redhat.com>
> ---
> drivers/gpu/drm/imagination/pvr_vm.c | 9 ++++++---
> drivers/gpu/drm/imagination/pvr_vm.h | 3 ++-
> 2 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/imagination/pvr_vm.c b/drivers/gpu/drm/imagination/pvr_vm.c
> index 09d481c575b0..1e89092c3dcc 100644
> --- a/drivers/gpu/drm/imagination/pvr_vm.c
> +++ b/drivers/gpu/drm/imagination/pvr_vm.c
> @@ -239,7 +239,7 @@ pvr_vm_bind_op_map_init(struct pvr_vm_bind_op *bind_op,
> return -EINVAL;
> }
>
> - if (!pvr_device_addr_and_size_are_valid(device_addr, size) ||
> + if (!pvr_device_addr_and_size_are_valid(vm_ctx, device_addr, size) ||
> offset & ~PAGE_MASK || size & ~PAGE_MASK ||
> offset >= pvr_obj_size || offset_plus_size > pvr_obj_size)
> return -EINVAL;
> @@ -295,7 +295,7 @@ pvr_vm_bind_op_unmap_init(struct pvr_vm_bind_op *bind_op,
> {
> int err;
>
> - if (!pvr_device_addr_and_size_are_valid(device_addr, size))
> + if (!pvr_device_addr_and_size_are_valid(vm_ctx, device_addr, size))
> return -EINVAL;
>
> bind_op->type = PVR_VM_BIND_TYPE_UNMAP;
> @@ -505,6 +505,7 @@ pvr_device_addr_is_valid(u64 device_addr)
> /**
> * pvr_device_addr_and_size_are_valid() - Tests whether a device-virtual
> * address and associated size are both valid.
> + * @vm_ctx: Target VM context.
> * @device_addr: Virtual device address to test.
> * @size: Size of the range based at @device_addr to test.
> *
> @@ -523,9 +524,11 @@ pvr_device_addr_is_valid(u64 device_addr)
> * * %false otherwise.
> */
> bool
> -pvr_device_addr_and_size_are_valid(u64 device_addr, u64 size)
> +pvr_device_addr_and_size_are_valid(struct pvr_vm_context *vm_ctx,
> + u64 device_addr, u64 size)
> {
> return pvr_device_addr_is_valid(device_addr) &&
> + drm_gpuvm_range_valid(&vm_ctx->gpuvm_mgr, device_addr, size) &&
> size != 0 && (size & ~PVR_DEVICE_PAGE_MASK) == 0 &&
> (device_addr + size <= PVR_PAGE_TABLE_ADDR_SPACE_SIZE);
> }
> diff --git a/drivers/gpu/drm/imagination/pvr_vm.h b/drivers/gpu/drm/imagination/pvr_vm.h
> index cf8b97553dc8..f2a6463f2b05 100644
> --- a/drivers/gpu/drm/imagination/pvr_vm.h
> +++ b/drivers/gpu/drm/imagination/pvr_vm.h
> @@ -29,7 +29,8 @@ struct drm_exec;
> /* Functions defined in pvr_vm.c */
>
> bool pvr_device_addr_is_valid(u64 device_addr);
> -bool pvr_device_addr_and_size_are_valid(u64 device_addr, u64 size);
> +bool pvr_device_addr_and_size_are_valid(struct pvr_vm_context *vm_ctx,
> + u64 device_addr, u64 size);
>
> struct pvr_vm_context *pvr_vm_create_context(struct pvr_device *pvr_dev,
> bool is_userspace_context);
next prev parent reply other threads:[~2023-11-28 10:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 23:36 [PATCH drm-misc-next 0/5] PowerVR VM fixes Danilo Krummrich
2023-11-24 23:36 ` [PATCH drm-misc-next 1/5] drm/imagination: vm: prevent duplicate drm_gpuvm_bo instances Danilo Krummrich
2023-11-28 10:34 ` [EXTERNAL] " Donald Robson
2023-11-28 13:00 ` (subset) " Maxime Ripard
2023-11-24 23:36 ` [PATCH drm-misc-next 2/5] drm/imagination: vm: check for drm_gpuvm_range_valid() Danilo Krummrich
2023-11-28 10:34 ` Donald Robson [this message]
2023-11-28 13:00 ` (subset) " Maxime Ripard
2023-11-24 23:36 ` [PATCH drm-misc-next 3/5] drm/imagination: vm: fix drm_gpuvm reference count Danilo Krummrich
2023-11-28 10:36 ` Donald Robson
2023-11-28 13:01 ` (subset) " Maxime Ripard
2023-11-24 23:36 ` [PATCH drm-misc-next 4/5] drm/gpuvm: fall back to drm_exec_lock_obj() Danilo Krummrich
2023-11-24 23:40 ` Danilo Krummrich
2023-11-27 13:52 ` Christian König
2023-11-27 17:50 ` Danilo Krummrich
2023-11-24 23:36 ` [PATCH drm-misc-next 5/5] drm/imagination: vm: make use of GPUVM's drm_exec helper Danilo Krummrich
2023-11-28 10:47 ` [EXTERNAL] " Donald Robson
2023-11-28 19:02 ` Danilo Krummrich
2023-11-27 10:53 ` [PATCH drm-misc-next 0/5] PowerVR VM fixes Frank Binns
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=bcd3a9fb156c773ac942818213e6192fe36dc6ac.camel@imgtec.com \
--to=donald.robson@imgtec.com \
--cc=Frank.Binns@imgtec.com \
--cc=Matt.Coster@imgtec.com \
--cc=Sarah.Walker@imgtec.com \
--cc=airlied@gmail.com \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
/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®