From: Boris Brezillon <boris.brezillon@collabora.com>
To: Danilo Krummrich <dakr@redhat.com>
Cc: matthew.brost@intel.com, thomas.hellstrom@linux.intel.com,
sarah.walker@imgtec.com, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
faith@gfxstrand.net, donald.robson@imgtec.com,
christian.koenig@amd.com
Subject: Re: [PATCH drm-misc-next v9 02/12] drm/gpuvm: don't always WARN in drm_gpuvm_check_overflow()
Date: Fri, 10 Nov 2023 12:19:58 +0100 [thread overview]
Message-ID: <20231110121958.59f9d330@collabora.com> (raw)
In-Reply-To: <20231108001259.15123-3-dakr@redhat.com>
On Wed, 8 Nov 2023 01:12:32 +0100
Danilo Krummrich <dakr@redhat.com> wrote:
> Don't always WARN in drm_gpuvm_check_overflow() and separate it into a
> drm_gpuvm_check_overflow() and a dedicated
> drm_gpuvm_warn_check_overflow() variant.
>
> This avoids printing warnings due to invalid userspace requests.
>
> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Signed-off-by: Danilo Krummrich <dakr@redhat.com>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
> ---
> drivers/gpu/drm/drm_gpuvm.c | 20 +++++++++++++-------
> 1 file changed, 13 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c
> index d7367a202fee..445767f8fbc4 100644
> --- a/drivers/gpu/drm/drm_gpuvm.c
> +++ b/drivers/gpu/drm/drm_gpuvm.c
> @@ -614,12 +614,18 @@ static int __drm_gpuva_insert(struct drm_gpuvm *gpuvm,
> static void __drm_gpuva_remove(struct drm_gpuva *va);
>
> static bool
> -drm_gpuvm_check_overflow(struct drm_gpuvm *gpuvm, u64 addr, u64 range)
> +drm_gpuvm_check_overflow(u64 addr, u64 range)
> {
> u64 end;
>
> - return drm_WARN(gpuvm->drm, check_add_overflow(addr, range, &end),
> - "GPUVA address limited to %zu bytes.\n", sizeof(end));
> + return check_add_overflow(addr, range, &end);
> +}
> +
> +static bool
> +drm_gpuvm_warn_check_overflow(struct drm_gpuvm *gpuvm, u64 addr, u64 range)
> +{
> + return drm_WARN(gpuvm->drm, drm_gpuvm_check_overflow(addr, range),
> + "GPUVA address limited to %zu bytes.\n", sizeof(addr));
> }
>
> static bool
> @@ -647,7 +653,7 @@ static bool
> drm_gpuvm_range_valid(struct drm_gpuvm *gpuvm,
> u64 addr, u64 range)
> {
> - return !drm_gpuvm_check_overflow(gpuvm, addr, range) &&
> + return !drm_gpuvm_check_overflow(addr, range) &&
> drm_gpuvm_in_mm_range(gpuvm, addr, range) &&
> !drm_gpuvm_in_kernel_node(gpuvm, addr, range);
> }
> @@ -682,7 +688,7 @@ drm_gpuvm_init(struct drm_gpuvm *gpuvm, const char *name,
> gpuvm->ops = ops;
> gpuvm->drm = drm;
>
> - drm_gpuvm_check_overflow(gpuvm, start_offset, range);
> + drm_gpuvm_warn_check_overflow(gpuvm, start_offset, range);
> gpuvm->mm_start = start_offset;
> gpuvm->mm_range = range;
>
> @@ -691,8 +697,8 @@ drm_gpuvm_init(struct drm_gpuvm *gpuvm, const char *name,
> gpuvm->kernel_alloc_node.va.addr = reserve_offset;
> gpuvm->kernel_alloc_node.va.range = reserve_range;
>
> - if (likely(!drm_gpuvm_check_overflow(gpuvm, reserve_offset,
> - reserve_range)))
> + if (likely(!drm_gpuvm_warn_check_overflow(gpuvm, reserve_offset,
> + reserve_range)))
> __drm_gpuva_insert(gpuvm, &gpuvm->kernel_alloc_node);
> }
> }
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Danilo Krummrich <dakr@redhat.com>
Cc: airlied@gmail.com, daniel@ffwll.ch, matthew.brost@intel.com,
thomas.hellstrom@linux.intel.com, sarah.walker@imgtec.com,
donald.robson@imgtec.com, christian.koenig@amd.com,
faith@gfxstrand.net, dri-devel@lists.freedesktop.org,
nouveau@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH drm-misc-next v9 02/12] drm/gpuvm: don't always WARN in drm_gpuvm_check_overflow()
Date: Fri, 10 Nov 2023 12:19:58 +0100 [thread overview]
Message-ID: <20231110121958.59f9d330@collabora.com> (raw)
In-Reply-To: <20231108001259.15123-3-dakr@redhat.com>
On Wed, 8 Nov 2023 01:12:32 +0100
Danilo Krummrich <dakr@redhat.com> wrote:
> Don't always WARN in drm_gpuvm_check_overflow() and separate it into a
> drm_gpuvm_check_overflow() and a dedicated
> drm_gpuvm_warn_check_overflow() variant.
>
> This avoids printing warnings due to invalid userspace requests.
>
> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Signed-off-by: Danilo Krummrich <dakr@redhat.com>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
> ---
> drivers/gpu/drm/drm_gpuvm.c | 20 +++++++++++++-------
> 1 file changed, 13 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c
> index d7367a202fee..445767f8fbc4 100644
> --- a/drivers/gpu/drm/drm_gpuvm.c
> +++ b/drivers/gpu/drm/drm_gpuvm.c
> @@ -614,12 +614,18 @@ static int __drm_gpuva_insert(struct drm_gpuvm *gpuvm,
> static void __drm_gpuva_remove(struct drm_gpuva *va);
>
> static bool
> -drm_gpuvm_check_overflow(struct drm_gpuvm *gpuvm, u64 addr, u64 range)
> +drm_gpuvm_check_overflow(u64 addr, u64 range)
> {
> u64 end;
>
> - return drm_WARN(gpuvm->drm, check_add_overflow(addr, range, &end),
> - "GPUVA address limited to %zu bytes.\n", sizeof(end));
> + return check_add_overflow(addr, range, &end);
> +}
> +
> +static bool
> +drm_gpuvm_warn_check_overflow(struct drm_gpuvm *gpuvm, u64 addr, u64 range)
> +{
> + return drm_WARN(gpuvm->drm, drm_gpuvm_check_overflow(addr, range),
> + "GPUVA address limited to %zu bytes.\n", sizeof(addr));
> }
>
> static bool
> @@ -647,7 +653,7 @@ static bool
> drm_gpuvm_range_valid(struct drm_gpuvm *gpuvm,
> u64 addr, u64 range)
> {
> - return !drm_gpuvm_check_overflow(gpuvm, addr, range) &&
> + return !drm_gpuvm_check_overflow(addr, range) &&
> drm_gpuvm_in_mm_range(gpuvm, addr, range) &&
> !drm_gpuvm_in_kernel_node(gpuvm, addr, range);
> }
> @@ -682,7 +688,7 @@ drm_gpuvm_init(struct drm_gpuvm *gpuvm, const char *name,
> gpuvm->ops = ops;
> gpuvm->drm = drm;
>
> - drm_gpuvm_check_overflow(gpuvm, start_offset, range);
> + drm_gpuvm_warn_check_overflow(gpuvm, start_offset, range);
> gpuvm->mm_start = start_offset;
> gpuvm->mm_range = range;
>
> @@ -691,8 +697,8 @@ drm_gpuvm_init(struct drm_gpuvm *gpuvm, const char *name,
> gpuvm->kernel_alloc_node.va.addr = reserve_offset;
> gpuvm->kernel_alloc_node.va.range = reserve_range;
>
> - if (likely(!drm_gpuvm_check_overflow(gpuvm, reserve_offset,
> - reserve_range)))
> + if (likely(!drm_gpuvm_warn_check_overflow(gpuvm, reserve_offset,
> + reserve_range)))
> __drm_gpuva_insert(gpuvm, &gpuvm->kernel_alloc_node);
> }
> }
next prev parent reply other threads:[~2023-11-10 11:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 0:12 [Nouveau] [PATCH drm-misc-next v9 00/12] [RFC] DRM GPUVM features Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 01/12] drm/gpuvm: convert WARN() to drm_WARN() variants Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 02/12] drm/gpuvm: don't always WARN in drm_gpuvm_check_overflow() Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-10 11:19 ` Boris Brezillon [this message]
2023-11-10 11:19 ` Boris Brezillon
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 03/12] drm/gpuvm: export drm_gpuvm_range_valid() Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-10 11:20 ` Boris Brezillon
2023-11-10 11:20 ` Boris Brezillon
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 04/12] drm/nouveau: make use of drm_gpuvm_range_valid() Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 05/12] drm/gpuvm: add common dma-resv per struct drm_gpuvm Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 06/12] drm/nouveau: make use of the GPUVM's shared dma-resv Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 07/12] drm/gpuvm: add drm_gpuvm_flags to drm_gpuvm Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 08/12] drm/nouveau: separately allocate struct nouveau_uvmm Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 09/12] drm/gpuvm: reference count drm_gpuvm structures Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-10 10:39 ` [Nouveau] " Thomas Hellström
2023-11-10 10:39 ` Thomas Hellström
2023-11-10 10:39 ` Thomas Hellström
2023-11-10 11:21 ` Boris Brezillon
2023-11-10 11:21 ` Boris Brezillon
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 10/12] drm/gpuvm: add an abstraction for a VM / BO combination Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 11/12] drm/gpuvm: track/lock/validate external/evicted objects Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` [Nouveau] [PATCH drm-misc-next v9 12/12] drm/nouveau: use GPUVM common infrastructure Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
2023-11-08 0:12 ` Danilo Krummrich
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=20231110121958.59f9d330@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dakr@redhat.com \
--cc=donald.robson@imgtec.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=faith@gfxstrand.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=nouveau@lists.freedesktop.org \
--cc=sarah.walker@imgtec.com \
--cc=thomas.hellstrom@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.