public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Eric Auger <eric.auger@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	stable@vger.kernel.org, sashal@kernel.org
Subject: Re: [PATCH 6.6.y 0/4] vfio: Interrupt eventfd hardening for 6.6.y
Date: Fri, 29 Mar 2024 12:53:18 +0100	[thread overview]
Message-ID: <2024032959-improve-groove-7bac@gregkh> (raw)
In-Reply-To: <bff69f62-692b-481e-bbad-020148894f7b@redhat.com>

On Thu, Mar 28, 2024 at 11:03:40AM +0100, Eric Auger wrote:
> Hi Alex,
> On 3/27/24 23:54, Alex Williamson wrote:
> > These backports only require reverting to the older eventfd_signal()
> > API with two parameters, prior to commit 3652117f8548
> > ("eventfd: simplify eventfd_signal()").  Thanks,
> for the series
> Reviewed-by: Eric Auger <eric.auger@redhat.com>

All now queued up, thanks.

But what about older kernels?  These should go much further back, right?

thanks,

greg k-h

      reply	other threads:[~2024-03-29 11:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 22:54 [PATCH 6.6.y 0/4] vfio: Interrupt eventfd hardening for 6.6.y Alex Williamson
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 [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=2024032959-improve-groove-7bac@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