From: Andi Shyti <andi.shyti@linux.intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: 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>,
Andi Shyti <andi.shyti@linux.intel.com>
Subject: [PATCH v2 0/2] Fix mmap memory boundary calculation
Date: Mon, 5 Aug 2024 11:25:52 +0100 [thread overview]
Message-ID: <20240805102554.154464-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.
Thanks a lot Jann for your inputs and reviews.
Rodrigo, could you please restate your review tag? I'm just
waiting for your tag in patch 1 to get this series in.
Thanks,
Andi
Changelog from v1:
==================
- Added Jonathan's and Jann's tags.
- pfn is now calculated inside the set_address_limits() as
suggested by Jonathan.
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 | 64 +++++++++++++++++++++---
1 file changed, 58 insertions(+), 6 deletions(-)
--
2.45.2
next reply other threads:[~2024-08-05 10:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 10:25 Andi Shyti [this message]
2024-08-05 10:25 ` [PATCH v2 1/2] drm/i915/gem: Adjust vma offset for framebuffer mmap offset Andi Shyti
2024-08-05 10:25 ` [PATCH v2 2/2] drm/i915/gem: Fix Virtual Memory mapping boundaries calculation Andi Shyti
2024-08-05 11:17 ` ✗ Fi.CI.CHECKPATCH: warning for Fix mmap memory boundary calculation (rev2) Patchwork
2024-08-05 11:25 ` ✓ Fi.CI.BAT: success " Patchwork
2024-08-05 19:36 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-08-05 22:05 ` [PATCH v2 0/2] Fix mmap memory boundary calculation Andi Shyti
2024-08-06 6:38 ` Greg Kroah-Hartman
2024-08-06 9:46 ` Andi Shyti
2024-08-06 12:08 ` Joonas Lahtinen
2024-08-09 14:48 ` Jann Horn
2024-08-09 15:40 ` Jann Horn
2024-08-12 9:18 ` Joonas Lahtinen
2024-08-12 12:30 ` Jann Horn
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=20240805102554.154464-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@google.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=krzysztof.niemiec@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