From: Alex Williamson <alex.williamson@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Jason Gunthorpe <jgg@ziepe.ca>,
David Laight <David.Laight@ACULAB.COM>,
"Tian, Kevin" <kevin.tian@intel.com>
Subject: Re: [PATCH v3 0/3] vfio: use __aligned_u64 for ioctl structs
Date: Thu, 28 Sep 2023 15:12:52 -0600 [thread overview]
Message-ID: <20230928151252.020dc019.alex.williamson@redhat.com> (raw)
In-Reply-To: <20230918205617.1478722-1-stefanha@redhat.com>
On Mon, 18 Sep 2023 16:56:14 -0400
Stefan Hajnoczi <stefanha@redhat.com> wrote:
> v3:
> - Remove the output struct sizing code that copied out zeroed fields at the end
> of the struct. Alex pointed out that new fields (or repurposing a field that
> was previously reserved) must be guarded by a flag and this means userspace
> won't access those fields when they are absent.
> v2:
> - Rebased onto https://github.com/awilliam/linux-vfio.git next to get the
> vfio_iommu_type1_info pad field [Kevin]
> - Fixed min(minsz, sizeof(dmabuf)) -> min(dmabuf.argsz, sizeof(dmabuf)) [Jason, Kevin]
> - Squashed Patch 3 (vfio_iommu_type1_info) into Patch 1 since it is trivial now
> that the padding field is already there.
>
> Jason Gunthorpe <jgg@nvidia.com> pointed out that u64 VFIO ioctl struct fields
> have architecture-dependent alignment. iommufd already uses __aligned_u64 to
> avoid this problem.
>
> See the __aligned_u64 typedef in <uapi/linux/types.h> for details on why it is
> a good idea for kernel<->user interfaces.
>
> This series modifies the VFIO ioctl structs to use __aligned_u64. Some of the
> changes preserve the existing memory layout on all architectures, so I put them
> together into the first patch. The remaining patches are for structs where
> explanation is necessary about why changing the memory layout does not break
> the uapi.
>
> Stefan Hajnoczi (3):
> vfio: trivially use __aligned_u64 for ioctl structs
> vfio: use __aligned_u64 in struct vfio_device_gfx_plane_info
> vfio: use __aligned_u64 in struct vfio_device_ioeventfd
>
> include/uapi/linux/vfio.h | 26 ++++++++++++++------------
> drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +-
> samples/vfio-mdev/mbochs.c | 2 +-
> samples/vfio-mdev/mdpy.c | 2 +-
> 4 files changed, 17 insertions(+), 15 deletions(-)
>
Applied to vfio next branch for v6.7. Thanks,
Alex
prev parent reply other threads:[~2023-09-28 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 20:56 Stefan Hajnoczi
2023-09-18 20:56 ` [PATCH v3 1/3] vfio: trivially " Stefan Hajnoczi
2023-09-18 20:56 ` [PATCH v3 2/3] vfio: use __aligned_u64 in struct vfio_device_gfx_plane_info Stefan Hajnoczi
2023-09-18 20:56 ` [PATCH v3 3/3] vfio: use __aligned_u64 in struct vfio_device_ioeventfd Stefan Hajnoczi
2023-09-28 21:12 ` Alex Williamson [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=20230928151252.020dc019.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=David.Laight@ACULAB.COM \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanha@redhat.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®