From: Stefan Hajnoczi <stefanha@redhat.com>
To: David Laight <David.Laight@aculab.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
"Tian, Kevin" <kevin.tian@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH 2/4] vfio: use __aligned_u64 in struct vfio_device_gfx_plane_info
Date: Wed, 16 Aug 2023 09:36:50 -0400 [thread overview]
Message-ID: <20230816133650.GC3425284@fedora> (raw)
In-Reply-To: <aff0d24d4bce4d34b27cfe6a76b0634e@AcuMS.aculab.com>
[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]
On Tue, Aug 15, 2023 at 03:23:50PM +0000, David Laight wrote:
> From: Stefan Hajnoczi
> > Sent: 09 August 2023 22:03
> >
> > The memory layout of struct vfio_device_gfx_plane_info is
> > architecture-dependent due to a u64 field and a struct size that is not
> > a multiple of 8 bytes:
> > - On x86_64 the struct size is padded to a multiple of 8 bytes.
> > - On x32 the struct size is only a multiple of 4 bytes, not 8.
> > - Other architectures may vary.
> >
> > Use __aligned_u64 to make memory layout consistent. This reduces the
> > chance of holes that result in an information leak and the chance that
> > 32-bit userspace on a 64-bit kernel breakage.
>
> Isn't the hole likely to cause an information leak?
> Forcing it to be there doesn't make any difference.
> I'd add an explicit pad as well.
Yes, Kevin had a similar comment about this text. What I meant was that
it's safest to have a single memory layout across all architectures
(with explicit padding) so that there are no surprises. I'm going to
remove the statement about information leaks because it's confusing.
>
> It is a shame there isn't an __attribute__(()) to error padded structures.
>
> >
> > This patch increases the struct size on x32 but this is safe because of
> > the struct's argsz field. The kernel may grow the struct as long as it
> > still supports smaller argsz values from userspace (e.g. applications
> > compiled against older kernel headers).
>
> Doesn't changing the offset of later fields break compatibility?
> The size field (probably) only lets you extend the structure.
Yes, that would break compatibility but I don't see any changes in this
patch series that modifies the offsets of later fields. Have I missed
something?
> Oh, for sanity do min(variable, constant).
Can you elaborate?
Thanks,
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-08-16 13:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 21:02 [PATCH 0/4] vfio: use __aligned_u64 for ioctl structs Stefan Hajnoczi
2023-08-09 21:02 ` [PATCH 1/4] vfio: trivially " Stefan Hajnoczi
2023-08-14 17:47 ` Jason Gunthorpe
2023-08-09 21:02 ` [PATCH 2/4] vfio: use __aligned_u64 in struct vfio_device_gfx_plane_info Stefan Hajnoczi
2023-08-10 3:22 ` Tian, Kevin
2023-08-10 14:24 ` Stefan Hajnoczi
2023-08-15 12:38 ` Stefan Hajnoczi
2023-08-14 17:50 ` Jason Gunthorpe
2023-08-15 12:38 ` Stefan Hajnoczi
2023-08-15 15:23 ` David Laight
2023-08-16 13:36 ` Stefan Hajnoczi [this message]
2023-08-09 21:02 ` [PATCH 3/4] vfio: use __aligned_u64 in struct vfio_iommu_type1_info Stefan Hajnoczi
2023-08-10 3:25 ` Tian, Kevin
2023-08-10 14:25 ` Stefan Hajnoczi
2023-08-14 17:52 ` Jason Gunthorpe
2023-08-09 21:02 ` [PATCH 4/4] vfio: use __aligned_u64 in struct vfio_device_ioeventfd Stefan Hajnoczi
2023-08-14 17:52 ` Jason Gunthorpe
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=20230816133650.GC3425284@fedora \
--to=stefanha@redhat.com \
--cc=David.Laight@aculab.com \
--cc=alex.williamson@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox