From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guangshuo Li <lgs201920130244@gmail.com>
Cc: Yaxing Guo <guoyaxing@bosc.ac.cn>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] uio: fix IRQ vector leak on probe failure and remove
Date: Fri, 17 Jul 2026 14:49:58 +0200 [thread overview]
Message-ID: <2026071752-morbidity-mourner-a2f9@gregkh> (raw)
In-Reply-To: <20260524064201.1177225-1-lgs201920130244@gmail.com>
On Sun, May 24, 2026 at 02:42:01PM +0800, Guangshuo Li wrote:
> probe() allocates MSI/MSI-X vectors with pci_alloc_irq_vectors(), but
> neither the error path nor remove() releases them with
> pci_free_irq_vectors().
>
> Unlike drivers using pcim_enable_device(), this driver uses
> pci_enable_device(), so the IRQ vectors are not managed automatically
> and must be freed explicitly.
>
> Add pci_free_irq_vectors() to the probe error path after successful
> vector allocation and to remove(). The issue was identified by a
> static analysis tool I developed.
>
> Fixes: 3397c3cd859a ("uio: Add SVA support for PCI devices via uio_pci_generic_sva.c")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
> ---
> v2:
> - Change have_irq_vectors from int to bool.
> - Set have_irq_vectors immediately after successful IRQ vector allocation.
>
> drivers/uio/uio_pci_generic_sva.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/uio/uio_pci_generic_sva.c b/drivers/uio/uio_pci_generic_sva.c
> index 4a46acd994a8..e216436c9116 100644
> --- a/drivers/uio/uio_pci_generic_sva.c
> +++ b/drivers/uio/uio_pci_generic_sva.c
> @@ -63,6 +63,7 @@ static int probe(struct pci_dev *pdev, const struct pci_device_id *id)
> {
> struct uio_pci_sva_dev *udev;
> int ret, i, irq = 0;
> + bool have_irq_vectors = false;
>
> ret = pci_enable_device(pdev);
> if (ret) {
> @@ -78,6 +79,8 @@ static int probe(struct pci_dev *pdev, const struct pci_device_id *id)
>
> ret = pci_alloc_irq_vectors(pdev, 1, 1, PCI_IRQ_MSIX | PCI_IRQ_MSI);
> if (ret > 0) {
> + have_irq_vectors = true;
> +
> irq = pci_irq_vector(pdev, 0);
> if (irq < 0) {
> dev_err(&pdev->dev, "Failed to get MSI vector\n");
> @@ -139,6 +142,8 @@ static int probe(struct pci_dev *pdev, const struct pci_device_id *id)
> out_free:
> kfree(udev);
> out_disable:
> + if (have_irq_vectors)
> + pci_free_irq_vectors(pdev);
> pci_disable_device(pdev);
>
> return ret;
> @@ -148,6 +153,7 @@ static void remove(struct pci_dev *pdev)
> {
> struct uio_pci_sva_dev *udev = pci_get_drvdata(pdev);
>
> + pci_free_irq_vectors(pdev);
> pci_release_regions(pdev);
> pci_disable_device(pdev);
> kfree(udev);
> --
> 2.43.0
>
>
Does not apply to linux-next :(
prev parent reply other threads:[~2026-07-17 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 6:42 Guangshuo Li
2026-07-17 12:49 ` Greg Kroah-Hartman [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=2026071752-morbidity-mourner-a2f9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=guoyaxing@bosc.ac.cn \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®