From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: stephen@networkplumber.org, hkalra@marvell.com
Subject: [PATCH 0/9] Interrupt fixes for leaks and warnings
Date: Wed, 21 Oct 2026 11:23:09 +0200 [thread overview]
Message-ID: <20261021092318.1554295-1-david.marchand@redhat.com> (raw)
Following commit d770ee9caed0 ("interrupts: warn on leaked FDs"), a
number of leaks, but also false positive warnings have been identified.
The most notable change in this series is the removal of the interrupt
handle duplication. I concluded the principle is wrong (see patch 2
commitlog).
This will need some careful reviews.
--
David Marchand
David Marchand (7):
eal/linux: reset FD in interrupt handle for uevent
interrupts: do not duplicate interrupt handles
net/mana: reset FD in interrupt handle
net/memif: fix some interrupt FD leaks
net/memif: reset FD in interrupt handle
net/sxe2: reset FD in interrupt handle
raw/ifpga: reset FD in interrupt handle
Stephen Hemminger (2):
eal/linux: fix FD leak in alarm subsystem
bus/pci: reset VFIO device FD after release
doc/guides/rel_notes/release_26_11.rst | 1 +
drivers/bus/pci/linux/pci_vfio.c | 4 ++--
drivers/common/cnxk/roc_platform.h | 1 -
drivers/net/mana/mana.c | 4 ++++
drivers/net/memif/memif_socket.c | 28 ++++++++++++++++++----
drivers/net/sxe2/sxe2_irq.c | 2 ++
drivers/raw/ifpga/ifpga_rawdev.c | 2 ++
lib/eal/common/eal_common_interrupts.c | 26 --------------------
lib/eal/freebsd/eal_interrupts.c | 17 ++++---------
lib/eal/include/rte_interrupts.h | 17 +------------
lib/eal/linux/eal_alarm.c | 1 +
lib/eal/linux/eal_dev.c | 4 ++--
lib/eal/linux/eal_interrupts.c | 33 ++++++++------------------
13 files changed, 53 insertions(+), 87 deletions(-)
--
2.54.0
next reply other threads:[~2026-10-21 9:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 9:23 David Marchand [this message]
2026-10-21 9:23 ` [PATCH 1/9] eal/linux: fix FD leak in alarm subsystem David Marchand
2026-10-21 9:23 ` [PATCH 2/9] eal/linux: reset FD in interrupt handle for uevent David Marchand
2026-10-21 9:23 ` [PATCH 3/9] interrupts: do not duplicate interrupt handles David Marchand
2026-10-21 9:23 ` [PATCH 4/9] bus/pci: reset VFIO device FD after release David Marchand
2026-10-21 9:23 ` [PATCH 5/9] net/mana: reset FD in interrupt handle David Marchand
2026-10-21 9:23 ` [PATCH 6/9] net/memif: fix some interrupt FD leaks David Marchand
2026-10-21 9:23 ` [PATCH 7/9] net/memif: reset FD in interrupt handle David Marchand
2026-10-21 9:23 ` [PATCH 8/9] net/sxe2: " David Marchand
2026-10-21 9:23 ` [PATCH 9/9] raw/ifpga: " David Marchand
2026-10-24 13:21 ` [PATCH v2 00/12] Interrupt fixes for leaks and warnings David Marchand
2026-10-24 13:21 ` [PATCH v2 01/12] eal/linux: fix FD leak in alarm subsystem David Marchand
2026-10-24 13:21 ` [PATCH v2 02/12] eal/linux: reset FD in interrupt handle for uevent David Marchand
2026-10-24 14:07 ` Burakov, Anatoly
2026-10-24 13:21 ` [PATCH v2 03/12] interrupts: do not duplicate interrupt handles David Marchand
2026-10-24 14:11 ` Burakov, Anatoly
2026-10-26 15:39 ` David Marchand
2026-10-24 13:21 ` [PATCH v2 04/12] bus/pci: reset VFIO device FD after release David Marchand
2026-10-24 14:11 ` Burakov, Anatoly
2026-10-24 13:21 ` [PATCH v2 05/12] net/mana: reset FD in interrupt handle David Marchand
2026-10-24 13:21 ` [PATCH v2 06/12] net/memif: fix some interrupt FD leaks David Marchand
2026-10-24 13:21 ` [PATCH v2 07/12] net/memif: reset FD in interrupt handle David Marchand
2026-10-24 13:21 ` [PATCH v2 08/12] net/sxe2: " David Marchand
2026-10-24 13:21 ` [PATCH v2 09/12] raw/ifpga: " David Marchand
2026-10-24 13:21 ` [PATCH v2 10/12] eal/linux: fix closing of event FDs not owned by EAL David Marchand
2026-10-24 13:21 ` [PATCH v2 11/12] eal/linux: fix eventfd leaks when enabling interrupts David Marchand
2026-10-24 13:21 ` [PATCH v2 12/12] interrupts: warn on leaked event FDs David Marchand
2026-10-27 17:16 ` [PATCH v2 00/12] Interrupt fixes for leaks and warnings David Marchand
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=20261021092318.1554295-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=stephen@networkplumber.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