From: Eric Auger <eric.auger@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, clg@redhat.com, reinette.chatre@intel.com,
linux-kernel@vger.kernel.org, kevin.tian@intel.com,
stable@vger.kernel.org
Subject: Re: [PATCH v2 2/7] vfio/pci: Lock external INTx masking ops
Date: Mon, 11 Mar 2024 10:14:33 +0100 [thread overview]
Message-ID: <2e2ec36a-3d48-48f0-8019-f1c1b320a477@redhat.com> (raw)
In-Reply-To: <20240308230557.805580-3-alex.williamson@redhat.com>
On 3/9/24 00:05, Alex Williamson wrote:
> Mask operations through config space changes to DisINTx may race INTx
> configuration changes via ioctl. Create wrappers that add locking for
> paths outside of the core interrupt code.
>
> In particular, irq_type is updated holding igate, therefore testing
> is_intx() requires holding igate. For example clearing DisINTx from
> config space can otherwise race changes of the interrupt configuration.
>
> This aligns interfaces which may trigger the INTx eventfd into two
> camps, one side serialized by igate and the other only enabled while
> INTx is configured. A subsequent patch introduces synchronization for
> the latter flows.
>
> Cc: stable@vger.kernel.org
> Fixes: 89e1f7d4c66d ("vfio: Add PCI device driver")
> Reported-by: Reinette Chatre <reinette.chatre@intel.com>
> Reviewed-by: Kevin Tian <kevin.tian@intel.com>
> Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Eric
> ---
> drivers/vfio/pci/vfio_pci_intrs.c | 34 +++++++++++++++++++++++++------
> 1 file changed, 28 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/vfio/pci/vfio_pci_intrs.c b/drivers/vfio/pci/vfio_pci_intrs.c
> index 136101179fcb..75c85eec21b3 100644
> --- a/drivers/vfio/pci/vfio_pci_intrs.c
> +++ b/drivers/vfio/pci/vfio_pci_intrs.c
> @@ -99,13 +99,15 @@ static void vfio_send_intx_eventfd(void *opaque, void *unused)
> }
>
> /* Returns true if the INTx vfio_pci_irq_ctx.masked value is changed. */
> -bool vfio_pci_intx_mask(struct vfio_pci_core_device *vdev)
> +static bool __vfio_pci_intx_mask(struct vfio_pci_core_device *vdev)
> {
> struct pci_dev *pdev = vdev->pdev;
> struct vfio_pci_irq_ctx *ctx;
> unsigned long flags;
> bool masked_changed = false;
>
> + lockdep_assert_held(&vdev->igate);
> +
> spin_lock_irqsave(&vdev->irqlock, flags);
>
> /*
> @@ -143,6 +145,17 @@ bool vfio_pci_intx_mask(struct vfio_pci_core_device *vdev)
> return masked_changed;
> }
>
> +bool vfio_pci_intx_mask(struct vfio_pci_core_device *vdev)
> +{
> + bool mask_changed;
> +
> + mutex_lock(&vdev->igate);
> + mask_changed = __vfio_pci_intx_mask(vdev);
> + mutex_unlock(&vdev->igate);
> +
> + return mask_changed;
> +}
> +
> /*
> * If this is triggered by an eventfd, we can't call eventfd_signal
> * or else we'll deadlock on the eventfd wait queue. Return >0 when
> @@ -194,12 +207,21 @@ static int vfio_pci_intx_unmask_handler(void *opaque, void *unused)
> return ret;
> }
>
> -void vfio_pci_intx_unmask(struct vfio_pci_core_device *vdev)
> +static void __vfio_pci_intx_unmask(struct vfio_pci_core_device *vdev)
> {
> + lockdep_assert_held(&vdev->igate);
> +
> if (vfio_pci_intx_unmask_handler(vdev, NULL) > 0)
> vfio_send_intx_eventfd(vdev, NULL);
> }
>
> +void vfio_pci_intx_unmask(struct vfio_pci_core_device *vdev)
> +{
> + mutex_lock(&vdev->igate);
> + __vfio_pci_intx_unmask(vdev);
> + mutex_unlock(&vdev->igate);
> +}
> +
> static irqreturn_t vfio_intx_handler(int irq, void *dev_id)
> {
> struct vfio_pci_core_device *vdev = dev_id;
> @@ -563,11 +585,11 @@ static int vfio_pci_set_intx_unmask(struct vfio_pci_core_device *vdev,
> return -EINVAL;
>
> if (flags & VFIO_IRQ_SET_DATA_NONE) {
> - vfio_pci_intx_unmask(vdev);
> + __vfio_pci_intx_unmask(vdev);
> } else if (flags & VFIO_IRQ_SET_DATA_BOOL) {
> uint8_t unmask = *(uint8_t *)data;
> if (unmask)
> - vfio_pci_intx_unmask(vdev);
> + __vfio_pci_intx_unmask(vdev);
> } else if (flags & VFIO_IRQ_SET_DATA_EVENTFD) {
> struct vfio_pci_irq_ctx *ctx = vfio_irq_ctx_get(vdev, 0);
> int32_t fd = *(int32_t *)data;
> @@ -594,11 +616,11 @@ static int vfio_pci_set_intx_mask(struct vfio_pci_core_device *vdev,
> return -EINVAL;
>
> if (flags & VFIO_IRQ_SET_DATA_NONE) {
> - vfio_pci_intx_mask(vdev);
> + __vfio_pci_intx_mask(vdev);
> } else if (flags & VFIO_IRQ_SET_DATA_BOOL) {
> uint8_t mask = *(uint8_t *)data;
> if (mask)
> - vfio_pci_intx_mask(vdev);
> + __vfio_pci_intx_mask(vdev);
> } else if (flags & VFIO_IRQ_SET_DATA_EVENTFD) {
> return -ENOTTY; /* XXX implement me */
> }
next prev parent reply other threads:[~2024-03-11 9:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 23:05 [PATCH v2 0/7] vfio: Interrupt eventfd hardening Alex Williamson
2024-03-08 23:05 ` [PATCH v2 1/7] vfio/pci: Disable auto-enable of exclusive INTx IRQ Alex Williamson
2024-03-11 7:36 ` Eric Auger
2024-03-11 14:40 ` Alex Williamson
2024-03-08 23:05 ` [PATCH v2 2/7] vfio/pci: Lock external INTx masking ops Alex Williamson
2024-03-11 9:14 ` Eric Auger [this message]
2024-03-08 23:05 ` [PATCH v2 3/7] vfio: Introduce interface to flush virqfd inject workqueue Alex Williamson
2024-03-11 9:14 ` Eric Auger
2024-03-08 23:05 ` [PATCH v2 4/7] vfio/pci: Create persistent INTx handler Alex Williamson
2024-03-11 9:15 ` Eric Auger
2024-03-08 23:05 ` [PATCH v2 5/7] vfio/platform: Disable virqfds on cleanup Alex Williamson
2024-03-11 1:55 ` Tian, Kevin
2024-03-11 9:16 ` Eric Auger
2024-03-08 23:05 ` [PATCH v2 6/7] vfio/platform: Create persistent IRQ handlers Alex Williamson
2024-03-11 1:55 ` Tian, Kevin
2024-03-11 9:27 ` Eric Auger
2024-03-15 16:36 ` Eric Auger
2024-03-08 23:05 ` [PATCH v2 7/7] vfio/fsl-mc: Block calling interrupt handler without trigger Alex Williamson
2024-03-11 1:56 ` Tian, Kevin
2024-03-11 9:29 ` Eric Auger
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=2e2ec36a-3d48-48f0-8019-f1c1b320a477@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--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
all inboxes | Powered by JetHome®