From: Alex Williamson <alex.williamson@nvidia.com>
To: Alex Williamson <alex@shazbot.org>, kvm <kvm@vger.kernel.org>
Cc: Alex Williamson <alex.williamson@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Kevin Tian <kevin.tian@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Yishai Hadas <yishaih@nvidia.com>,
rananta@google.com
Subject: [PATCH v2 0/2] vfio: Fix racy bitfields and tighten struct layout
Date: Mon, 11 May 2026 16:16:01 -0600 [thread overview]
Message-ID: <20260511221609.3837652-1-alex.williamson@nvidia.com> (raw)
A recent patch[1] proposed by Raghavendra triggered a Sashiko
review[2] flagging that the proposed new bitfield shares storage
with neighbors and that concurrent updates via RMW may clobber
adjacent fields.
Auditing bitfield users in vfio_pci_core_device finds several
pre-existing fields with the same hazard, and an analogous pattern
in mlx5_vhca_page_tracker / mlx5vf_pci_core_device. This series
splits all such fields out of their shared storage words, resolving
the existing cases.
v2: Uncouple from Raghavendra's patch so that Sashiko can apply
and review (new field dropped), we can handle merge on commit.
Thanks,
Alex
[1] https://lore.kernel.org/all/20260504224142.1041477-1-rananta@google.com/
[2] https://sashiko.dev/#/patchset/20260504224142.1041477-1-rananta@google.com
Alex Williamson (2):
vfio/pci: Fix racy bitfields and tighten struct layout
vfio/mlx5: Fix racy bitfields and tighten struct layout
drivers/vfio/pci/mlx5/cmd.h | 8 ++++----
include/linux/vfio_pci_core.h | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)
--
2.51.0
next reply other threads:[~2026-05-11 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 22:16 Alex Williamson [this message]
2026-05-11 22:16 ` [PATCH v2 1/2] vfio/pci: Fix racy bitfields and tighten struct layout Alex Williamson
2026-05-12 13:17 ` David Laight
2026-05-12 13:26 ` Alex Williamson
2026-05-12 13:18 ` Jason Gunthorpe
2026-05-11 22:16 ` [PATCH v2 2/2] vfio/mlx5: " Alex Williamson
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=20260511221609.3837652-1-alex.williamson@nvidia.com \
--to=alex.williamson@nvidia.com \
--cc=alex@shazbot.org \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rananta@google.com \
--cc=yishaih@nvidia.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