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: gustavoars@kernel.org, trix@redhat.com, dlatypov@google.com,
	llvm@lists.linux.dev, linux@rasmusvillemoes.dk,
	dri-devel@lists.freedesktop.org, chris@chris-wilson.co.uk,
	linux-hardening@vger.kernel.org, andrzej.hajda@intel.com,
	linux-sparse@vger.kernel.org, matthew.auld@intel.com,
	andi.shyti@linux.intel.com, airlied@redhat.com,
	thomas.hellstrom@linux.intel.com, keescook@chromium.org,
	jani.nikula@intel.com, nathan@kernel.org, mchehab@kernel.org,
	mauro.chehab@linux.intel.com, ndesaulniers@google.com,
	linux-kernel@vger.kernel.org, vitor@massaru.org,
	luc.vanoostenryck@gmail.com, nirmoy.das@intel.com
Subject: [PATCH v13 7/9] drm/i915: Check if the size is too big while creating shmem file
Date: Wed, 28 Sep 2022 11:12:58 +0300	[thread overview]
Message-ID: <20220928081300.101516-8-gwan-gyeong.mun@intel.com> (raw)
In-Reply-To: <20220928081300.101516-1-gwan-gyeong.mun@intel.com>

The __shmem_file_setup() function returns -EINVAL if size is greater than
MAX_LFS_FILESIZE. To handle the same error as other code that returns
-E2BIG when the size is too large, it add a code that returns -E2BIG when
the size is larger than the size that can be handled.

v4: If BITS_PER_LONG is 32, size > MAX_LFS_FILESIZE is always false, so it
    checks only when BITS_PER_LONG is 64.

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>
Reported-by: kernel test robot <lkp@intel.com>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
---
 drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
index 339b0a9cf2d0..ca30060e34ab 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
@@ -541,6 +541,20 @@ static int __create_shmem(struct drm_i915_private *i915,
 
 	drm_gem_private_object_init(&i915->drm, obj, size);
 
+	/* XXX: The __shmem_file_setup() function returns -EINVAL if size is
+	 * greater than MAX_LFS_FILESIZE.
+	 * To handle the same error as other code that returns -E2BIG when
+	 * the size is too large, we add a code that returns -E2BIG when the
+	 * size is larger than the size that can be handled.
+	 * If BITS_PER_LONG is 32, size > MAX_LFS_FILESIZE is always false,
+	 * so we only needs to check when BITS_PER_LONG is 64.
+	 * If BITS_PER_LONG is 32, E2BIG checks are processed when
+	 * i915_gem_object_size_2big() is called before init_object() callback
+	 * is called.
+	 */
+	if (BITS_PER_LONG == 64 && size > MAX_LFS_FILESIZE)
+		return -E2BIG;
+
 	if (i915->mm.gemfs)
 		filp = shmem_file_setup_with_mnt(i915->mm.gemfs, "i915", size,
 						 flags);
-- 
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: gustavoars@kernel.org, trix@redhat.com, dlatypov@google.com,
	llvm@lists.linux.dev, linux@rasmusvillemoes.dk,
	dri-devel@lists.freedesktop.org, chris@chris-wilson.co.uk,
	linux-hardening@vger.kernel.org, andrzej.hajda@intel.com,
	linux-sparse@vger.kernel.org, matthew.auld@intel.com,
	airlied@redhat.com, thomas.hellstrom@linux.intel.com,
	keescook@chromium.org, jani.nikula@intel.com, nathan@kernel.org,
	mchehab@kernel.org, ndesaulniers@google.com,
	linux-kernel@vger.kernel.org, daniel@ffwll.ch, vitor@massaru.org,
	luc.vanoostenryck@gmail.com, nirmoy.das@intel.com
Subject: [Intel-gfx] [PATCH v13 7/9] drm/i915: Check if the size is too big while creating shmem file
Date: Wed, 28 Sep 2022 11:12:58 +0300	[thread overview]
Message-ID: <20220928081300.101516-8-gwan-gyeong.mun@intel.com> (raw)
In-Reply-To: <20220928081300.101516-1-gwan-gyeong.mun@intel.com>

The __shmem_file_setup() function returns -EINVAL if size is greater than
MAX_LFS_FILESIZE. To handle the same error as other code that returns
-E2BIG when the size is too large, it add a code that returns -E2BIG when
the size is larger than the size that can be handled.

v4: If BITS_PER_LONG is 32, size > MAX_LFS_FILESIZE is always false, so it
    checks only when BITS_PER_LONG is 64.

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>
Reported-by: kernel test robot <lkp@intel.com>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
---
 drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
index 339b0a9cf2d0..ca30060e34ab 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
@@ -541,6 +541,20 @@ static int __create_shmem(struct drm_i915_private *i915,
 
 	drm_gem_private_object_init(&i915->drm, obj, size);
 
+	/* XXX: The __shmem_file_setup() function returns -EINVAL if size is
+	 * greater than MAX_LFS_FILESIZE.
+	 * To handle the same error as other code that returns -E2BIG when
+	 * the size is too large, we add a code that returns -E2BIG when the
+	 * size is larger than the size that can be handled.
+	 * If BITS_PER_LONG is 32, size > MAX_LFS_FILESIZE is always false,
+	 * so we only needs to check when BITS_PER_LONG is 64.
+	 * If BITS_PER_LONG is 32, E2BIG checks are processed when
+	 * i915_gem_object_size_2big() is called before init_object() callback
+	 * is called.
+	 */
+	if (BITS_PER_LONG == 64 && size > MAX_LFS_FILESIZE)
+		return -E2BIG;
+
 	if (i915->mm.gemfs)
 		filp = shmem_file_setup_with_mnt(i915->mm.gemfs, "i915", size,
 						 flags);
-- 
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,
	trix@redhat.com, llvm@lists.linux.dev,
	linux-hardening@vger.kernel.org, linux-sparse@vger.kernel.org,
	nathan@kernel.org, gustavoars@kernel.org,
	luc.vanoostenryck@gmail.com
Subject: [PATCH v13 7/9] drm/i915: Check if the size is too big while creating shmem file
Date: Wed, 28 Sep 2022 11:12:58 +0300	[thread overview]
Message-ID: <20220928081300.101516-8-gwan-gyeong.mun@intel.com> (raw)
In-Reply-To: <20220928081300.101516-1-gwan-gyeong.mun@intel.com>

The __shmem_file_setup() function returns -EINVAL if size is greater than
MAX_LFS_FILESIZE. To handle the same error as other code that returns
-E2BIG when the size is too large, it add a code that returns -E2BIG when
the size is larger than the size that can be handled.

v4: If BITS_PER_LONG is 32, size > MAX_LFS_FILESIZE is always false, so it
    checks only when BITS_PER_LONG is 64.

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>
Reported-by: kernel test robot <lkp@intel.com>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
---
 drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
index 339b0a9cf2d0..ca30060e34ab 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
@@ -541,6 +541,20 @@ static int __create_shmem(struct drm_i915_private *i915,
 
 	drm_gem_private_object_init(&i915->drm, obj, size);
 
+	/* XXX: The __shmem_file_setup() function returns -EINVAL if size is
+	 * greater than MAX_LFS_FILESIZE.
+	 * To handle the same error as other code that returns -E2BIG when
+	 * the size is too large, we add a code that returns -E2BIG when the
+	 * size is larger than the size that can be handled.
+	 * If BITS_PER_LONG is 32, size > MAX_LFS_FILESIZE is always false,
+	 * so we only needs to check when BITS_PER_LONG is 64.
+	 * If BITS_PER_LONG is 32, E2BIG checks are processed when
+	 * i915_gem_object_size_2big() is called before init_object() callback
+	 * is called.
+	 */
+	if (BITS_PER_LONG == 64 && size > MAX_LFS_FILESIZE)
+		return -E2BIG;
+
 	if (i915->mm.gemfs)
 		filp = shmem_file_setup_with_mnt(i915->mm.gemfs, "i915", size,
 						 flags);
-- 
2.37.1


  parent reply	other threads:[~2022-09-28  8:14 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  8:12 [PATCH v13 0/9] Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation Gwan-gyeong Mun
2022-09-28  8:12 ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-28  8:12 ` Gwan-gyeong Mun
2022-09-28  8:12 ` [PATCH v13 1/9] overflow: Allow mixed type arguments Gwan-gyeong Mun
2022-09-28  8:12   ` Gwan-gyeong Mun
2022-09-28  8:12   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-28  8:12 ` [PATCH v13 2/9] overflow: Introduce check_assign() and check_assign_user_ptr() Gwan-gyeong Mun
2022-09-28  8:12   ` Gwan-gyeong Mun
2022-09-28  8:12   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-28  8:12 ` [PATCH v13 3/9] overflow: Introduce overflows_type() and castable_to_type() Gwan-gyeong Mun
2022-09-28  8:12   ` Gwan-gyeong Mun
2022-09-28  8:12   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-28  8:12 ` [Intel-gfx] [PATCH v13 4/9] drm/i915/gem: Typecheck page lookups Gwan-gyeong Mun
2022-09-28  8:12   ` Gwan-gyeong Mun
2022-09-28  8:12   ` Gwan-gyeong Mun
2022-09-28  8:12 ` [PATCH v13 5/9] drm/i915: Check for integer truncation on scatterlist creation Gwan-gyeong Mun
2022-09-28  8:12   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-28  8:12   ` Gwan-gyeong Mun
2022-09-28  8:51   ` Jani Nikula
2022-09-28  8:51     ` [Intel-gfx] " Jani Nikula
2022-09-28  8:51     ` Jani Nikula
2022-10-07 16:38     ` Gwan-gyeong Mun
2022-10-07 16:38       ` [Intel-gfx] " Gwan-gyeong Mun
2022-10-07 16:38       ` Gwan-gyeong Mun
2022-09-28 17:09   ` Linus Torvalds
2022-09-28 17:09     ` [Intel-gfx] " Linus Torvalds
2022-09-28 17:09     ` Linus Torvalds
2022-09-28 18:06     ` Kees Cook
2022-09-28 18:06       ` Kees Cook
2022-09-28 18:06       ` [Intel-gfx] " Kees Cook
2022-10-07 16:40       ` Gwan-gyeong Mun
2022-10-07 16:40         ` [Intel-gfx] " Gwan-gyeong Mun
2022-10-07 16:40         ` Gwan-gyeong Mun
2022-10-07 16:45     ` Gwan-gyeong Mun
2022-10-07 16:45       ` [Intel-gfx] " Gwan-gyeong Mun
2022-10-07 16:45       ` Gwan-gyeong Mun
2022-09-28  8:12 ` [PATCH v13 6/9] drm/i915: Check for integer truncation on the configuration of ttm place Gwan-gyeong Mun
2022-09-28  8:12   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-28  8:12   ` Gwan-gyeong Mun
2022-09-28  8:12 ` Gwan-gyeong Mun [this message]
2022-09-28  8:12   ` [PATCH v13 7/9] drm/i915: Check if the size is too big while creating shmem file Gwan-gyeong Mun
2022-09-28  8:12   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-28  8:12 ` [PATCH v13 8/9] drm/i915: Use error code as -E2BIG when the size of gem ttm object is too large Gwan-gyeong Mun
2022-09-28  8:12   ` Gwan-gyeong Mun
2022-09-28  8:12   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-28  8:13 ` [PATCH v13 9/9] drm/i915: Remove truncation warning for large objects Gwan-gyeong Mun
2022-09-28  8:13   ` Gwan-gyeong Mun
2022-09-28  8:13   ` [Intel-gfx] " Gwan-gyeong Mun
2022-09-28 14:35 ` [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-28 14:35 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-09-28 14:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-29  8:44 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20220928081300.101516-8-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=gustavoars@kernel.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=llvm@lists.linux.dev \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=matthew.auld@intel.com \
    --cc=mauro.chehab@linux.intel.com \
    --cc=mchehab@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nirmoy.das@intel.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=trix@redhat.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.