All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: [PATCH 0/3] drm/xe: Userptr invalid page access fixes
Date: Fri, 28 Feb 2025 11:44:15 +0100	[thread overview]
Message-ID: <20250228104418.44313-1-thomas.hellstrom@linux.intel.com> (raw)

Fix a number of potential invalid page-accesses by the userptr code.

Patch 1:
- Some coding style fixes.
Patch 2:
- Avoids invalid struct page accesses during userptr pinning.
Patch 3:
- Block xe device accesses on mmu_invalidation on the iommu level.

Thomas Hellström (3):
  drm/xe/hmm: Style- and include fixes
  drm/xe/hmm: Don't dereference struct page pointers without notifier
    lock
  drm/xe/userptr: Unmap userptrs in the mmu notifier

 drivers/gpu/drm/xe/xe_hmm.c      | 165 +++++++++++++++++++++++--------
 drivers/gpu/drm/xe/xe_hmm.h      |   7 ++
 drivers/gpu/drm/xe/xe_vm.c       |   4 +
 drivers/gpu/drm/xe/xe_vm_types.h |   4 +
 4 files changed, 139 insertions(+), 41 deletions(-)

-- 
2.48.1


             reply	other threads:[~2025-02-28 10:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 10:44 Thomas Hellström [this message]
2025-02-28 10:44 ` [PATCH 1/3] drm/xe/hmm: Style- and include fixes Thomas Hellström
2025-02-28 12:56   ` Matthew Auld
2025-02-28 10:44 ` [PATCH 2/3] drm/xe/hmm: Don't dereference struct page pointers without notifier lock Thomas Hellström
2025-02-28 12:55   ` Matthew Auld
2025-02-28 13:08     ` Thomas Hellström
2025-02-28 18:32       ` Matthew Auld
2025-03-04 11:28         ` Thomas Hellström
2025-02-28 10:44 ` [PATCH 3/3] drm/xe/userptr: Unmap userptrs in the mmu notifier Thomas Hellström
2025-02-28 12:08 ` ✗ CI.Patch_applied: failure for drm/xe: Userptr invalid page access fixes 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=20250228104418.44313-1-thomas.hellstrom@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.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.