From: Abdifatah Suruur <suruurism@gmail.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: alex@shazbot.org, eric.auger@redhat.com, smostafa@google.com,
praan@google.com, ioana.ciornei@nxp.com, nipun.gupta@amd.com,
nikhil.agarwal@amd.com
Subject: [PATCH 0/7] vfio: mmap()/mprotect() hygiene for MMIO region mappings
Date: Mon, 21 Sep 2026 15:23:27 +0300 [thread overview]
Message-ID: <20260921122334.2099-1-suruurism@gmail.com> (raw)
These seven patches are hygiene/hardening cleanups of the MMIO region
mmap() paths in vfio-platform, vfio/fsl-mc and vfio/cdx, all in the
same class as commit a5edadbae57e ("ptp: vmclock: prevent read-only
mappings from becoming writable"). They do two things:
1. Clear VM_MAYWRITE on regions without VFIO_REGION_INFO_FLAG_WRITE
so that mprotect() cannot upgrade a read-only MMIO mapping to
writable (patches 1-3).
2. Keep vma->vm_pgoff in the logical VFIO offset space instead of
overwriting it with the physical frame number, and reject
non-shared mmaps where the remap_pfn_range() COW special case
would overwrite it anyway (patches 4-7).
Proper scoping: no in-tree platform, fsl-mc or cdx device currently
publishes a region without the WRITE flag, and none of the three
drivers calls unmap_mapping_range(), so none of these issues is
reachable today. The vm_pgoff changes preserve the documented VFIO
core contract that every device mmap is linked to the device inode's
i_mapping so it can be revoked; that shared namespace came from
commit b7c5e64fecfa ("vfio: Create vfio_fs_type with inode per device"), so
Fixes: tags were dropped from patches 4-7 and kept on patches 1-3,
pointing at the commits that added each driver's MMIO mmap support.
Previously posted as standalone patches; grouping them into one series
per Alex's request. Reviewed-by tags from those reviews are carried
on the affected patches.
Abdifatah Suruur (7):
vfio/platform: prevent read-only region mappings from becoming
writable
vfio/fsl-mc: prevent read-only region mappings from becoming
writable
vfio/cdx: prevent read-only region mappings from becoming writable
vfio/platform: keep logical vm_pgoff in MMIO region mmap
vfio/fsl-mc: keep logical vm_pgoff in MMIO region mmap
vfio/cdx: keep logical vm_pgoff in MMIO region mmap
vfio/cdx: reject non-shared MMIO mmaps
drivers/vfio/cdx/main.c | 11 +++++++++--
drivers/vfio/fsl-mc/vfio_fsl_mc.c | 9 ++++++---
drivers/vfio/platform/vfio_platform_common.c | 15 +++++++++------
3 files changed, 24 insertions(+), 11 deletions(-)
next reply other threads:[~2026-09-21 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 12:23 Abdifatah Suruur [this message]
2026-09-21 12:23 ` [PATCH 1/7] vfio/platform: prevent read-only region mappings from becoming writable Abdifatah Suruur
2026-09-21 12:23 ` [PATCH 2/7] vfio/fsl-mc: " Abdifatah Suruur
2026-09-21 12:23 ` [PATCH 3/7] vfio/cdx: " Abdifatah Suruur
2026-09-21 12:23 ` [PATCH 4/7] vfio/platform: keep logical vm_pgoff in MMIO region mmap Abdifatah Suruur
2026-09-21 12:23 ` [PATCH 5/7] vfio/fsl-mc: " Abdifatah Suruur
2026-09-21 12:23 ` [PATCH 6/7] vfio/cdx: " Abdifatah Suruur
2026-09-21 12:23 ` [PATCH 7/7] vfio/cdx: reject non-shared MMIO mmaps Abdifatah Suruur
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=20260921122334.2099-1-suruurism@gmail.com \
--to=suruurism@gmail.com \
--cc=alex@shazbot.org \
--cc=eric.auger@redhat.com \
--cc=ioana.ciornei@nxp.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.com \
--cc=praan@google.com \
--cc=smostafa@google.com \
/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
all inboxes | Powered by JetHome®