Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Cc: Jann Horn <jannh@chromium.org>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	Jann Horn <jannh@google.com>,
	Chris Wilson <chris.p.wilson@linux.intel.com>,
	Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
	Andi Shyti <andi.shyti@kernel.org>,
	Matthew Auld <matthew.auld@intel.com>,
	Andi Shyti <andi.shyti@linux.intel.com>
Subject: [PATCH 0/2] Fix mmap memory boundary calculation
Date: Fri,  2 Aug 2024 10:38:48 +0200	[thread overview]
Message-ID: <20240802083850.103694-1-andi.shyti@linux.intel.com> (raw)

Hi,

this series fixes the memory limits calculation (start, end), in
order to avoid access to addresses not belonging to the mapped
page.

This series has been reviewed in other communities but, because
it needs to go through drm-tip, I am proposing it again here in
the intel-gfx mailing list.

Jann, Rodrigo, could you please restate your review tag?

Thanks,
Andi

Andi Shyti (2):
  drm/i915/gem: Adjust vma offset for framebuffer mmap offset
  drm/i915/gem: Fix Virtual Memory mapping boundaries calculation

 drivers/gpu/drm/i915/gem/i915_gem_mman.c | 55 +++++++++++++++++++++---
 1 file changed, 49 insertions(+), 6 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-08-02  8:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02  8:38 Andi Shyti [this message]
2024-08-02  8:38 ` [PATCH 1/2] drm/i915/gem: Adjust vma offset for framebuffer mmap offset Andi Shyti
2024-08-02 17:08   ` Cavitt, Jonathan
2024-08-05 21:12   ` Rodrigo Vivi
2024-08-02  8:38 ` [PATCH 2/2] drm/i915/gem: Fix Virtual Memory mapping boundaries calculation Andi Shyti
2024-08-02  8:43   ` Jann Horn
2024-08-02 17:25   ` Cavitt, Jonathan
2024-08-05  9:39     ` Andi Shyti
2024-08-02  9:04 ` ✗ Fi.CI.CHECKPATCH: warning for Fix mmap memory boundary calculation Patchwork
2024-08-02  9:20 ` ✓ Fi.CI.BAT: success " Patchwork
2024-08-02 19:57 ` ✗ Fi.CI.IGT: failure " 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=20240802083850.103694-1-andi.shyti@linux.intel.com \
    --to=andi.shyti@linux.intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=chris.p.wilson@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=jannh@chromium.org \
    --cc=jannh@google.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=krzysztof.niemiec@intel.com \
    --cc=matthew.auld@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=tursulin@ursulin.net \
    /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