From: Thomas Gleixner <tglx@kernel.org>
To: neilfsun <loyou85@gmail.com>, 18255117159@163.com
Cc: bhelgaas@google.com, hans.zhang@cixtech.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
loyou85@gmail.com, neilfsun@tencent.com,
shawn.lin@rock-chips.com
Subject: Re: [PATCH v2 v2] PCI/MSI: Fix memory leak in pci_alloc_irq_vectors_affinity INTx path
Date: Tue, 21 Apr 2026 10:06:21 +0200 [thread overview]
Message-ID: <878qagd9fm.ffs@tglx> (raw)
In-Reply-To: <20260421032044.55948-1-neilfsun@tencent.com>
On Tue, Apr 21 2026 at 11:20, neilfsun wrote:
Please use function() notation in the subject as well.
> In the INTx fallback path of pci_alloc_irq_vectors_affinity(),
> affinity masks are created and never freed.
And then?
https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#changelog
This also lacks a Fixes: tag to identify the commit which introduced the
problem. Hint: It was not commit beddb5efb43ee.
> Signed-off-by: neilfsun <neilfsun@tencent.com>
^^^^^^^^
Please provide your real name and not your nickname. See
Documentation/process/...
> Signed-off-by: Sun Feng <loyou85@gmail.com>
This Signed-off-by chain is broken. See Documentation/process/...
> Reviewed-by: Hans Zhang <18255117159@163.com>
Hans did not provide you a Reviewed-by tag. The fact that he reviewed V1
and made suggestions how to improve does not imply that.
> @@ -285,8 +285,10 @@ int pci_alloc_irq_vectors_affinity(struct pci_dev *dev, unsigned int min_vecs,
> * the device driver can adjust queue configuration
> * for the single interrupt case.
> */
> - if (affd)
> - irq_create_affinity_masks(1, affd);
> + if (affd) {
> + struct irq_affinity_desc *masks __free(kfree) =
> + irq_create_affinity_masks(1, affd);
There is no point to use __free() here. The only reason why this is
invoked for the INTX case is to ensure that the affinity descriptor is
updated and an eventually provided calc_sets() callback is invoked. The
returned mask is not used at all, so this can be simplified to:
kfree(affd ? irq_create_affinity_masks(1, affd) : NULL);
Along with a proper comment.
Thanks,
tglx
prev parent reply other threads:[~2026-04-21 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 4:09 [PATCH] PCI/MSI: Fix memory leak in pci_alloc_irq_vectors_affinity INTx path neilfsun
2026-04-20 4:47 ` Hans Zhang
2026-04-21 3:20 ` [PATCH v2 v2] " neilfsun
2026-04-21 6:24 ` Shawn Lin
2026-04-21 8:06 ` Thomas Gleixner [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=878qagd9fm.ffs@tglx \
--to=tglx@kernel.org \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=hans.zhang@cixtech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=loyou85@gmail.com \
--cc=neilfsun@tencent.com \
--cc=shawn.lin@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox