From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: Harman Kalra <hkalra@marvell.com>,
dev@dpdk.org, "Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [RFC 0/3] fix bogus interrupt FD leak warnings
Date: Mon, 19 Oct 2026 10:20:50 -0700 [thread overview]
Message-ID: <20261019102050.3f4c4c50@phoenix.local> (raw)
In-Reply-To: <CAJFAV8x9JDsQdxEispOeAcRGsPT9erxGx_c2EHMVWqH-KQV1JQ@mail.gmail.com>
On Mon, 19 Oct 2026 16:12:30 +0200
David Marchand <david.marchand@redhat.com> wrote:
> > - Patch 2 resets dev_fd at the two unmap sites. Doing it inside
> > dev_vfio_release_device(), next to the close, would cover any other
> > caller.
>
> The current fix is a symetric to the map path, where the VFIO
> subsystem gives back to the PCI bus a device FD tracked in the
> interrupt handle object of the PCI device object.
>
> The VFIO subsytem has no idea about the intr handle stuff.
> All it knows about is the device FD, which seems correctly closed by
> VFIO on call to dev_vfio_release_device() indeed.
>
> I don't see why it should change, can you clarify?
Not sure, these patches were AI generated, based off of
"I see these warnings now in testpmd, where are they coming from and fix"
prev parent reply other threads:[~2026-10-19 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 20:35 [RFC 0/3] fix bogus interrupt FD leak warnings Stephen Hemminger
2026-10-17 20:35 ` [RFC 1/3] eal/linux: do not warn when freeing interrupt source copy Stephen Hemminger
2026-10-17 20:35 ` [RFC 2/3] bus/pci: reset VFIO device FD after release Stephen Hemminger
2026-10-17 20:35 ` [RFC 3/3] eal/linux: close alarm timerfd on cleanup Stephen Hemminger
2026-10-19 14:12 ` [RFC 0/3] fix bogus interrupt FD leak warnings David Marchand
2026-10-19 17:20 ` Stephen Hemminger [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=20261019102050.3f4c4c50@phoenix.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.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.