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 5.10.y 5.4.y 0/6] vfio: Interrupt eventfd hardening for 5.10.y, 5.4.y
Date: Fri, 5 Apr 2024 11:16:29 +0200 [thread overview]
Message-ID: <2024040519-monument-carwash-cfd0@gregkh> (raw)
In-Reply-To: <20240401165302.3699643-1-alex.williamson@redhat.com>
On Mon, Apr 01, 2024 at 10:52:54AM -0600, Alex Williamson wrote:
> This is nearly identical to the v5.15 backport, the only difference is
> the split to struct vfio_pci_core_device hasn't occurred yet, so we need
> to use the original vfio_pci_device object instead.
>
> NB. The fsl-mc driver doesn't exist on v5.4.y, therefore the last patch
> in the series should be dropped against v5.4.
>
> v4.19.y does not include IRQF_NO_AUTOEN, so this is as far as I intend
> to go with these. Thanks,
All now queued up, thanks!
greg k-h
prev parent reply other threads:[~2024-04-05 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 16:52 [PATCH 5.10.y 5.4.y 0/6] vfio: Interrupt eventfd hardening for 5.10.y, 5.4.y Alex Williamson
2024-04-01 16:52 ` [PATCH 5.10.y 5.4.y 1/6] vfio/pci: Disable auto-enable of exclusive INTx IRQ Alex Williamson
2024-04-01 16:52 ` [PATCH 5.10.y 5.4.y 2/6] vfio/pci: Lock external INTx masking ops Alex Williamson
2024-04-01 16:52 ` [PATCH 5.10.y 5.4.y 3/6] vfio: Introduce interface to flush virqfd inject workqueue Alex Williamson
2024-04-01 16:52 ` [PATCH 5.10.y 5.4.y 4/6] vfio/pci: Create persistent INTx handler Alex Williamson
2024-04-01 16:52 ` [PATCH 5.10.y 5.4.y 5/6] vfio/platform: Create persistent IRQ handlers Alex Williamson
2024-04-01 16:53 ` [PATCH 5.10.y 6/6] vfio/fsl-mc: Block calling interrupt handler without trigger Alex Williamson
2024-04-05 9:16 ` 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=2024040519-monument-carwash-cfd0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox