From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Willy Tarreau <w@1wt.eu>,
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>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Chris Wilson <chris@chris-wilson.co.uk>,
Matthew Auld <matthew.auld@intel.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Shrikanth Hegde <sshegde@linux.ibm.com>,
Rik van Riel <riel@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linuxppc-dev@lists.ozlabs.org, "Chris Mason" <mason@kernel.org>,
stable@vger.kernel.org, "Felix Kuehling" <Felix.Kuehling@amd.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 0/5] mm,drm/i915,powerpc/spufs: vm_ops->access related fixes
Date: Sat, 14 Nov 2026 17:17:27 +0100 [thread overview]
Message-ID: <beb98f9c-c6fb-4bf6-962a-46f542a19c53@kernel.org> (raw)
In-Reply-To: <20261112-access_shite-v1-0-988a5c470db2@kernel.org>
On 11/12/26 23:08, David Hildenbrand (Arm) wrote:
> While working on vm_ops->access related fixes in core code for FOLL_ANON
> and VMA access permission + size handling, I stumbled over two driver
> issues. Also, I have to update one selftest that specifies PROT_WRITE
> but actually wants read-access.
>
> Fixing it all in this series, because it's all intertwined.
>
> In patch #5 we break a debugging use case for older ROCm versions, where
> the amdgpu driver hacked around it by exploiting broken access checks in
> core-mm.
>
> Tested as good as I can with selftests. I cannot really test the
> i915 and powerpc/spufs stuff on real hardware.
>
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
> ---
> Chris Mason (1):
> mm: do not call vm_ops->access with FOLL_ANON
>
> David Hildenbrand (Arm) (4):
> drm/i915: consider vm_pgoff in vm_access()
> drm/i915/selftests: request read access for mmap access tests
> powerpc/spufs: consider vm_pgoff in spufs_mem_mmap_access()
> mm: check permissions and bounds for vm_ops->access
>
> arch/powerpc/platforms/cell/spufs/file.c | 3 ++-
> drivers/gpu/drm/i915/gem/i915_gem_mman.c | 4 +++-
> drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c | 3 ++-
> mm/memory.c | 28 ++++++++++++++++++++--
> 4 files changed, 33 insertions(+), 5 deletions(-)
>
We get some test failures regarding error handling: e.g.,
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_178442v1/shard-glk6/igt@gem_mmap_offset@oob-read.html
It's all about error handling.
Before the correct handling in patch #5, we would pass a size that exceeds the
actual VMA to vm_access(), and that one would return -EIO.
In the test above 8 bytes whereby the VMA only allowed for 4 more bytes.
Now we properly handle that in core code and get a partial read completion on
the 4 bytes.
I think the test should be fixed to expect a partial read completion.
We won't hack around this in core-mm.
--
Cheers,
David
prev parent reply other threads:[~2026-11-14 16:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 22:08 [PATCH 0/5] mm,drm/i915,powerpc/spufs: vm_ops->access related fixes David Hildenbrand (Arm)
2026-11-12 22:08 ` [PATCH 1/5] mm: do not call vm_ops->access with FOLL_ANON David Hildenbrand (Arm)
2026-11-14 18:56 ` Lorenzo Stoakes (ARM)
2026-11-12 22:08 ` [PATCH 2/5] drm/i915: consider vm_pgoff in vm_access() David Hildenbrand (Arm)
2026-11-14 18:58 ` Lorenzo Stoakes (ARM)
2026-11-12 22:08 ` [PATCH 3/5] drm/i915/selftests: request read access for mmap access tests David Hildenbrand (Arm)
2026-11-14 18:58 ` Lorenzo Stoakes (ARM)
2026-11-12 22:09 ` [PATCH 4/5] powerpc/spufs: consider vm_pgoff in spufs_mem_mmap_access() David Hildenbrand (Arm)
2026-11-14 18:59 ` Lorenzo Stoakes (ARM)
2026-11-12 22:09 ` [PATCH 5/5] mm: check permissions and bounds for vm_ops->access David Hildenbrand (Arm)
2026-11-13 20:25 ` Kuehling, Felix
2026-11-13 21:37 ` David Hildenbrand (Arm)
2026-11-14 19:08 ` Lorenzo Stoakes (ARM)
2026-11-13 1:50 ` ✓ i915.CI.BAT: success for mm,drm/i915,powerpc/spufs: vm_ops->access related fixes Patchwork
2026-11-14 3:28 ` ✗ i915.CI.Full: failure " Patchwork
2026-11-14 16:17 ` David Hildenbrand (Arm) [this message]
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=beb98f9c-c6fb-4bf6-962a-46f542a19c53@kernel.org \
--to=david@kernel.org \
--cc=Felix.Kuehling@amd.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=chleroy@kernel.org \
--cc=chris@chris-wilson.co.uk \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ljs@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mason@kernel.org \
--cc=matthew.auld@intel.com \
--cc=mhocko@suse.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=riel@redhat.com \
--cc=ritesh.list@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=rppt@kernel.org \
--cc=simona@ffwll.ch \
--cc=sshegde@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=tursulin@ursulin.net \
--cc=vbabka@kernel.org \
--cc=w@1wt.eu \
/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.