From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: stable@vger.kernel.org, sashal@kernel.org, eric.auger@redhat.com
Subject: Re: [PATCH 6.1.y 0/7] vfio: Interrupt eventfd hardening for 6.6.y
Date: Sat, 30 Mar 2024 09:54:57 +0100 [thread overview]
Message-ID: <2024033041-unleash-wrinkle-4b2a@gregkh> (raw)
In-Reply-To: <20240329213856.2550762-1-alex.williamson@redhat.com>
On Fri, Mar 29, 2024 at 03:38:47PM -0600, Alex Williamson wrote:
> This corrects the backport of commit fe9a7082684e ("vfio/pci: Disable
> auto-enable of exclusive INTx IRQ"), choosing to adapt the fix to the
> current tree which uses an array of eventfd contexts rather than
> include a base patch for the conversion to xarray, which is found to
> be faulty in isolation.
>
> I include the reverts here for completeness, but if the associated
> commits are otherwise already dropped due to previous report[1], the
> remainder of this series is still valid.
Remainder of the series is now queued up, thanks!
greg k-h
prev parent reply other threads:[~2024-03-30 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 21:38 [PATCH 6.1.y 0/7] vfio: Interrupt eventfd hardening for 6.6.y Alex Williamson
2024-03-29 21:38 ` [PATCH 6.1.y 1/7] Revert "vfio/pci: Disable auto-enable of exclusive INTx IRQ" Alex Williamson
2024-03-30 8:46 ` Greg KH
2024-03-29 21:38 ` [PATCH 6.1.y 2/7] Revert "vfio/pci: Prepare for dynamic interrupt context storage" Alex Williamson
2024-03-30 8:46 ` Greg KH
2024-03-29 21:38 ` [PATCH 6.1.y 3/7] vfio/pci: Disable auto-enable of exclusive INTx IRQ Alex Williamson
2024-03-29 21:38 ` [PATCH 6.1.y 4/7] vfio: Introduce interface to flush virqfd inject workqueue Alex Williamson
2024-03-29 21:38 ` [PATCH 6.1.y 5/7] vfio/pci: Create persistent INTx handler Alex Williamson
2024-03-29 21:38 ` [PATCH 6.1.y 6/7] vfio/platform: Create persistent IRQ handlers Alex Williamson
2024-03-29 21:38 ` [PATCH 6.1.y 7/7] vfio/fsl-mc: Block calling interrupt handler without trigger Alex Williamson
2024-03-30 8:54 ` Greg KH [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=2024033041-unleash-wrinkle-4b2a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=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.