All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: thomas.hellstrom@linux.intel.com, mauro.chehab@linux.intel.com,
	andi.shyti@linux.intel.com, keescook@chromium.org,
	jani.nikula@intel.com, ndesaulniers@google.com,
	dlatypov@google.com, linux@rasmusvillemoes.dk,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	chris@chris-wilson.co.uk, andrzej.hajda@intel.com,
	matthew.auld@intel.com, airlied@redhat.com, mchehab@kernel.org,
	vitor@massaru.org, nirmoy.das@intel.com
Subject: [PATCH v11 8/9] drm/i915: Use error code as -E2BIG when the size of gem ttm object is too large
Date: Fri, 23 Sep 2022 11:26:27 +0300	[thread overview]
Message-ID: <20220923082628.3061408-9-gwan-gyeong.mun@intel.com> (raw)
In-Reply-To: <20220923082628.3061408-1-gwan-gyeong.mun@intel.com>

The ttm_bo_init_reserved() functions returns -ENOSPC if the size is too big
to add vma. The direct function that returns -ENOSPC is drm_mm_insert_node_in_range().
To handle the same error as other code returning -E2BIG when the size is
too large, it converts return value to -E2BIG.

Signed-off-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Matthew Auld <matthew.auld@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
---
 drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
index e6bbc0f8b7e6..62d3924a6377 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
@@ -1242,6 +1242,17 @@ int __i915_gem_ttm_object_init(struct intel_memory_region *mem,
 	ret = ttm_bo_init_reserved(&i915->bdev, i915_gem_to_ttm(obj), bo_type,
 				   &i915_sys_placement, page_size >> PAGE_SHIFT,
 				   &ctx, NULL, NULL, i915_ttm_bo_destroy);
+
+	/*
+	 * XXX: The ttm_bo_init_reserved() functions returns -ENOSPC if the size
+	 * is too big to add vma. The direct function that returns -ENOSPC is
+	 * drm_mm_insert_node_in_range(). To handle the same error as other code
+	 * that returns -E2BIG when the size is too large, it converts -ENOSPC to
+	 * -E2BIG.
+	 */
+	if (size >> PAGE_SHIFT > INT_MAX && ret == -ENOSPC)
+		ret = -E2BIG;
+
 	if (ret)
 		return i915_ttm_err_to_gem(ret);
 
-- 
2.37.1


WARNING: multiple messages have this Message-ID (diff)
From: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: thomas.hellstrom@linux.intel.com, keescook@chromium.org,
	jani.nikula@intel.com, ndesaulniers@google.com,
	dlatypov@google.com, linux@rasmusvillemoes.dk,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	chris@chris-wilson.co.uk, andrzej.hajda@intel.com,
	matthew.auld@intel.com, daniel@ffwll.ch, airlied@redhat.com,
	mchehab@kernel.org, vitor@massaru.org, nirmoy.das@intel.com
Subject: [Intel-gfx] [PATCH v11 8/9] drm/i915: Use error code as -E2BIG when the size of gem ttm object is too large
Date: Fri, 23 Sep 2022 11:26:27 +0300	[thread overview]
Message-ID: <20220923082628.3061408-9-gwan-gyeong.mun@intel.com> (raw)
In-Reply-To: <20220923082628.3061408-1-gwan-gyeong.mun@intel.com>

The ttm_bo_init_reserved() functions returns -ENOSPC if the size is too big
to add vma. The direct function that returns -ENOSPC is drm_mm_insert_node_in_range().
To handle the same error as other code returning -E2BIG when the size is
too large, it converts return value to -E2BIG.

Signed-off-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Matthew Auld <matthew.auld@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
---
 drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
index e6bbc0f8b7e6..62d3924a6377 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
@@ -1242,6 +1242,17 @@ int __i915_gem_ttm_object_init(struct intel_memory_region *mem,
 	ret = ttm_bo_init_reserved(&i915->bdev, i915_gem_to_ttm(obj), bo_type,
 				   &i915_sys_placement, page_size >> PAGE_SHIFT,
 				   &ctx, NULL, NULL, i915_ttm_bo_destroy);
+
+	/*
+	 * XXX: The ttm_bo_init_reserved() functions returns -ENOSPC if the size
+	 * is too big to add vma. The direct function that returns -ENOSPC is
+	 * drm_mm_insert_node_in_range(). To handle the same error as other code
+	 * that returns -E2BIG when the size is too large, it converts -ENOSPC to
+	 * -E2BIG.
+	 */
+	if (size >> PAGE_SHIFT > INT_MAX && ret == -ENOSPC)
+		ret = -E2BIG;
+
 	if (ret)
 		return i915_ttm_err_to_gem(ret);
 
-- 
2.37.1


WARNING: multiple messages have this Message-ID (diff)
From: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	mchehab@kernel.org, chris@chris-wilson.co.uk,
	matthew.auld@intel.com, thomas.hellstrom@linux.intel.com,
	jani.nikula@intel.com, nirmoy.das@intel.com, airlied@redhat.com,
	daniel@ffwll.ch, andi.shyti@linux.intel.com,
	andrzej.hajda@intel.com, keescook@chromium.org,
	mauro.chehab@linux.intel.com, linux@rasmusvillemoes.dk,
	vitor@massaru.org, dlatypov@google.com, ndesaulniers@google.com
Subject: [PATCH v11 8/9] drm/i915: Use error code as -E2BIG when the size of gem ttm object is too large
Date: Fri, 23 Sep 2022 11:26:27 +0300	[thread overview]
Message-ID: <20220923082628.3061408-9-gwan-gyeong.mun@intel.com> (raw)
In-Reply-To: <20220923082628.3061408-1-gwan-gyeong.mun@intel.com>

The ttm_bo_init_reserved() functions returns -ENOSPC if the size is too big
to add vma. The direct function that returns -ENOSPC is drm_mm_insert_node_in_range().
To handle the same error as other code returning -E2BIG when the size is
too large, it converts return value to -E2BIG.

Signed-off-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Matthew Auld <matthew.auld@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
---
 drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
index e6bbc0f8b7e6..62d3924a6377 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
@@ -1242,6 +1242,17 @@ int __i915_gem_ttm_object_init(struct intel_memory_region *mem,
 	ret = ttm_bo_init_reserved(&i915->bdev, i915_gem_to_ttm(obj), bo_type,
 				   &i915_sys_placement, page_size >> PAGE_SHIFT,
 				   &ctx, NULL, NULL, i915_ttm_bo_destroy);
+
+	/*
+	 * XXX: The ttm_bo_init_reserved() functions returns -ENOSPC if the size
+	 * is too big to add vma. The direct function that returns -ENOSPC is
+	 * drm_mm_insert_node_in_range(). To handle the same error as other code
+	 * that returns -E2BIG when the size is too large, it converts -ENOSPC to
+	 * -E2BIG.
+	 */
+	if (size >> PAGE_SHIFT > INT_MAX && ret == -ENOSPC)
+		ret = -E2BIG;
+
 	if (ret)
 		return i915_ttm_err_to_gem(ret);
 
-- 
2.37.1


  parent reply	other threads:[~2022-09-23  8:27 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  8:26 [PATCH v11 0/9] Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation Gwan-gyeong Mun
2022-09-23  8:26 ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-23  8:26 ` Gwan-gyeong Mun
2022-09-23  8:26 ` [PATCH v11 1/9] overflow: Allow mixed type arguments Gwan-gyeong Mun
2022-09-23  8:26   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-23  8:26   ` Gwan-gyeong Mun
2022-09-23  8:26 ` [PATCH v11 2/9] overflow: Move and add few utility macros into overflow Gwan-gyeong Mun
2022-09-23  8:26   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-23  8:26   ` Gwan-gyeong Mun
2022-09-23  8:26 ` [PATCH v11 3/9] compiler_types.h: Add assert_same_type to catch type mis-match while compiling Gwan-gyeong Mun
2022-09-23  8:26   ` Gwan-gyeong Mun
2022-09-23  8:26   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-24  4:21   ` kernel test robot
2022-09-24  4:21     ` [Intel-gfx] " kernel test robot
2022-09-24  4:21     ` kernel test robot
2022-09-24 14:52   ` kernel test robot
2022-09-24 14:52     ` [Intel-gfx] " kernel test robot
2022-09-24 14:52     ` kernel test robot
2022-09-26  0:37   ` Kees Cook
2022-09-26  0:37     ` Kees Cook
2022-09-26  0:37     ` [Intel-gfx] " Kees Cook
2022-09-26  0:37     ` [PATCH v11.5] overflow: Introduce overflows_type() and __castable_to_type() Kees Cook
2022-09-26  0:37       ` [Intel-gfx] " Kees Cook
2022-09-26  0:37       ` Kees Cook
2022-09-26  9:53       ` Gwan-gyeong Mun
2022-09-26  9:53         ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-26  9:53         ` Gwan-gyeong Mun
2022-09-26 15:57       ` Gwan-gyeong Mun
2022-09-26 15:57         ` Gwan-gyeong Mun
2022-09-26 15:57         ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-26 17:49         ` Kees Cook
2022-09-26 17:49           ` [Intel-gfx] " Kees Cook
2022-09-26 17:49           ` Kees Cook
2022-09-23  8:26 ` [PATCH v11 4/9] drm/i915/gem: Typecheck page lookups Gwan-gyeong Mun
2022-09-23  8:26   ` Gwan-gyeong Mun
2022-09-23  8:26   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-23  8:26 ` [Intel-gfx] [PATCH v11 5/9] drm/i915: Check for integer truncation on scatterlist creation Gwan-gyeong Mun
2022-09-23  8:26   ` Gwan-gyeong Mun
2022-09-23  8:26   ` Gwan-gyeong Mun
2022-09-23  8:26 ` [PATCH v11 6/9] drm/i915: Check for integer truncation on the configuration of ttm place Gwan-gyeong Mun
2022-09-23  8:26   ` Gwan-gyeong Mun
2022-09-23  8:26   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-23  8:26 ` [PATCH v11 7/9] drm/i915: Check if the size is too big while creating shmem file Gwan-gyeong Mun
2022-09-23  8:26   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-23  8:26   ` Gwan-gyeong Mun
2022-09-23  8:26 ` Gwan-gyeong Mun [this message]
2022-09-23  8:26   ` [PATCH v11 8/9] drm/i915: Use error code as -E2BIG when the size of gem ttm object is too large Gwan-gyeong Mun
2022-09-23  8:26   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-23  8:26 ` [PATCH v11 9/9] drm/i915: Remove truncation warning for large objects Gwan-gyeong Mun
2022-09-23  8:26   ` Gwan-gyeong Mun
2022-09-23  8:26   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-23 10:49 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation Patchwork
2022-09-23 10:49 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-09-23 11:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-23 23:04 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-09-26  0:41 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation (rev2) Patchwork

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=20220923082628.3061408-9-gwan-gyeong.mun@intel.com \
    --to=gwan-gyeong.mun@intel.com \
    --cc=airlied@redhat.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dlatypov@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=matthew.auld@intel.com \
    --cc=mauro.chehab@linux.intel.com \
    --cc=mchehab@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nirmoy.das@intel.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=vitor@massaru.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 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.