All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: stable@vger.kernel.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
	eric.auger@redhat.com, sashal@kernel.org
Subject: [PATCH 6.6.y 0/4] vfio: Interrupt eventfd hardening for 6.6.y
Date: Wed, 27 Mar 2024 16:54:26 -0600	[thread overview]
Message-ID: <20240327225444.909882-1-alex.williamson@redhat.com> (raw)

These backports only require reverting to the older eventfd_signal()
API with two parameters, prior to commit 3652117f8548
("eventfd: simplify eventfd_signal()").  Thanks,

Alex

Alex Williamson (4):
  vfio: Introduce interface to flush virqfd inject workqueue
  vfio/pci: Create persistent INTx handler
  vfio/platform: Create persistent IRQ handlers
  vfio/fsl-mc: Block calling interrupt handler without trigger

 drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c    |   7 +-
 drivers/vfio/pci/vfio_pci_intrs.c         | 145 ++++++++++++----------
 drivers/vfio/platform/vfio_platform_irq.c | 100 ++++++++++-----
 drivers/vfio/virqfd.c                     |  21 ++++
 include/linux/vfio.h                      |   2 +
 5 files changed, 173 insertions(+), 102 deletions(-)

-- 
2.44.0


             reply	other threads:[~2024-03-27 22:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 22:54 Alex Williamson [this message]
2024-03-27 22:54 ` [PATCH 6.6.y 1/4] vfio: Introduce interface to flush virqfd inject workqueue Alex Williamson
2024-03-27 22:54 ` [PATCH 6.6.y 2/4] vfio/pci: Create persistent INTx handler Alex Williamson
2024-03-27 22:54 ` [PATCH 6.6.y 3/4] vfio/platform: Create persistent IRQ handlers Alex Williamson
2024-03-27 22:54 ` [PATCH 6.6.y 4/4] vfio/fsl-mc: Block calling interrupt handler without trigger Alex Williamson
2024-03-28 10:03 ` [PATCH 6.6.y 0/4] vfio: Interrupt eventfd hardening for 6.6.y Eric Auger
2024-03-29 11:53   ` Greg KH

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=20240327225444.909882-1-alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=sashal@kernel.org \
    --cc=stable@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 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.