From: "Michael S. Tsirkin" <mst@redhat.com>
To: Xiong Weimin <xiongweimin@kylinos.cn>
Cc: virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
"Jason Wang" <jasowangio@gmail.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] virtio_pci: do not mutate caller irq_affinity.pre_vectors
Date: Wed, 5 Aug 2026 01:37:01 -0400 [thread overview]
Message-ID: <20260805013203-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20260805032934.1606700-1-xiongweimin@kylinos.cn>
On Wed, Aug 05, 2026 at 11:29:34AM +0800, Xiong Weimin wrote:
> vp_request_msix_vectors() bumps desc->pre_vectors in place to reserve
> the virtio config vector. vp_find_vqs() may call it more than once while
> retrying MSI-X with different per-vq policies, so the caller's
> irq_affinity keeps accumulating and later attempts get the wrong
> affinity layout.
>
> Copy the descriptor to a stack local, adjust pre_vectors there, and
> pass that to pci_alloc_irq_vectors_affinity().
>
> Fixes: ba74b6f7fcc0 ("virtio_pci: fix cpu affinity support")
> Cc: stable@vger.kernel.org
> Signed-off-by: Xiong Weimin <xiongweimin@kylinos.cn>
> ---
> drivers/virtio/virtio_pci_common.c | 16 ++++++++++------
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/virtio/virtio_pci_common.c b/drivers/virtio/virtio_pci_common.c
> index 164f480b1..9e75fd03e 100644
> --- a/drivers/virtio/virtio_pci_common.c
> +++ b/drivers/virtio/virtio_pci_common.c
> @@ -128,6 +128,7 @@ static int vp_request_msix_vectors(struct virtio_device *vdev, int nvectors,
> {
> struct virtio_pci_device *vp_dev = to_vp_device(vdev);
> const char *name = dev_name(&vp_dev->vdev.dev);
> + struct irq_affinity tmp_aff, *aff = NULL;
"tmp" in what sense? if we can come up with a sensible name, just
"affinity" will do.
> unsigned int flags = PCI_IRQ_MSIX;
> unsigned int i, v;
> int err = -ENOMEM;
> @@ -146,16 +147,19 @@ static int vp_request_msix_vectors(struct virtio_device *vdev, int nvectors,
> GFP_KERNEL))
> goto error;
>
> - if (!per_vq_vectors)
> - desc = NULL;
> -
> - if (desc) {
> + if (per_vq_vectors && desc) {
> + /*
> + * Do not mutate the caller's irq_affinity across MSI-X
> + * fallback retries in vp_find_vqs().
> + */
We do not need a comment arguing with previous version of the code.
> + tmp_aff = *desc;
> + tmp_aff.pre_vectors++; /* virtio config vector */
> + aff = &tmp_aff;
just assign to desc, instead?
> flags |= PCI_IRQ_AFFINITY;
> - desc->pre_vectors++; /* virtio config vector */
> }
>
> err = pci_alloc_irq_vectors_affinity(vp_dev->pci_dev, nvectors,
> - nvectors, flags, desc);
> + nvectors, flags, aff);
> if (err < 0)
> goto error;
> vp_dev->msix_enabled = 1;
> --
> 2.43.0
next prev parent reply other threads:[~2026-08-05 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 3:29 [PATCH] virtio_pci: do not mutate caller irq_affinity.pre_vectors Xiong Weimin
2026-08-05 5:37 ` Michael S. Tsirkin [this message]
2026-08-05 6:47 ` Xiong Weimin
2026-08-05 6:59 ` Michael S. Tsirkin
2026-08-05 6:19 ` Xiong Weimin
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=20260805013203-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=jasowangio@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=xiongweimin@kylinos.cn \
--cc=xuanzhuo@linux.alibaba.com \
/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.