From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Large page offsets for pread/pwrite
Date: Fri, 12 Oct 2018 15:41:35 +0100 [thread overview]
Message-ID: <7dc53bed-e3d6-632f-9eb5-689fefc02311@linux.intel.com> (raw)
In-Reply-To: <20181012140228.29783-1-chris@chris-wilson.co.uk>
On 12/10/2018 15:02, Chris Wilson wrote:
> Handle integer overflow when computing the sub-page length for shmem
> backed pread/pwrite.
>
> Reported-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/gpu/drm/i915/i915_gem.c | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 7d45e71100bc..93d09282710d 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -1127,11 +1127,7 @@ i915_gem_shmem_pread(struct drm_i915_gem_object *obj,
> offset = offset_in_page(args->offset);
> for (idx = args->offset >> PAGE_SHIFT; remain; idx++) {
> struct page *page = i915_gem_object_get_page(obj, idx);
> - int length;
> -
> - length = remain;
> - if (offset + length > PAGE_SIZE)
> - length = PAGE_SIZE - offset;
> + unsigned int length = min_t(u64, remain, PAGE_SIZE - offset);
>
> ret = shmem_pread(page, offset, length, user_data,
> page_to_phys(page) & obj_do_bit17_swizzling,
> @@ -1575,11 +1571,7 @@ i915_gem_shmem_pwrite(struct drm_i915_gem_object *obj,
> offset = offset_in_page(args->offset);
> for (idx = args->offset >> PAGE_SHIFT; remain; idx++) {
> struct page *page = i915_gem_object_get_page(obj, idx);
> - int length;
> -
> - length = remain;
> - if (offset + length > PAGE_SIZE)
> - length = PAGE_SIZE - offset;
> + unsigned int length = min_t(u64, remain, PAGE_SIZE - offset);
>
> ret = shmem_pwrite(page, offset, length, user_data,
> page_to_phys(page) & obj_do_bit17_swizzling,
>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
next prev parent reply other threads:[~2018-10-12 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 14:02 [PATCH] drm/i915: Large page offsets for pread/pwrite Chris Wilson
2018-10-12 14:12 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2018-10-12 14:29 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-12 14:41 ` Tvrtko Ursulin [this message]
2018-10-12 16:01 ` ✓ 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=7dc53bed-e3d6-632f-9eb5-689fefc02311@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.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