From: David Marchand <david.marchand@redhat.com>
To: Owen Hilyard <ohilyard@iol.unh.edu>
Cc: dev <dev@dpdk.org>, dpdklab <dpdklab@iol.unh.edu>,
Gaetan Rivet <grive@u256.net>
Subject: Re: [dpdk-dev] Memory leak in rte_pci_scan
Date: Mon, 14 Jun 2021 11:11:41 +0200 [thread overview]
Message-ID: <CAJFAV8yoZkDAxaLwPLftYLMoJM-4k2QM9CMYi8k5aFhLq0WW5A@mail.gmail.com> (raw)
In-Reply-To: <CAHx6DYA72dPcPcrW1UgJL7mq6H2g4pE3BxN95gitvmR8LV++qQ@mail.gmail.com>
On Tue, Jun 8, 2021 at 8:48 PM Owen Hilyard <ohilyard@iol.unh.edu> wrote:
>
> Hello All,
>
> As part of the community lab's work to deploy static analysis tools, we've
> been doing test runs of the various tools. One of the problems we found is
> that rte_pci_scan leaks 214368 Bytes every time it is run. There are also
I suspect the "leak" is on pci device objects that are not released
unless hot(un)plugging.
Cc: Gaetan.
> numerous (180856) instances of the error message "EAL: recvmsg failed, Bad
> file descriptor". Attached is the log from running the fast-tests suite
> with ASAN enabled, and a 10-second timeout. The real timeout seems to be
> the timeout argument multiplied by 10, making this really a 100-second
> timeout. It is attached as a google drive link since the log itself is too
> large for the mailing list.
Those logs come from the mp channel.
At cleanup the rte_mp_handle control thread is sleeping on the mp socket.
The thread serving rte_eal_cleanup shutdowns this socket fd, and the
control thread will spew the log messages you saw.
I'll send a patch.
--
David Marchand
next prev parent reply other threads:[~2021-06-14 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 18:47 Owen Hilyard
2021-06-14 9:11 ` David Marchand [this message]
2021-06-14 10:30 ` David Marchand
2021-06-14 20:41 ` Owen Hilyard
2021-06-15 7:43 ` David Marchand
2021-06-15 15:15 ` Owen Hilyard
2021-06-16 9:37 ` David Marchand
[not found] ` <CAHx6DYAADd4b9U8m7hNk0d_KkxgYuLF7_ntf+q57tE39W0H2bQ@mail.gmail.com>
2021-06-16 17:40 ` 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=CAJFAV8yoZkDAxaLwPLftYLMoJM-4k2QM9CMYi8k5aFhLq0WW5A@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=grive@u256.net \
--cc=ohilyard@iol.unh.edu \
/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;
as well as URLs for NNTP newsgroup(s).