From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 447] ixgbe: ixgbe_dev_link_update_share() leaks memory and memory mappings due to not cleaning up pthreads
Date: Thu, 09 Apr 2020 17:26:01 +0000 [thread overview]
Message-ID: <bug-447-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=447
Bug ID: 447
Summary: ixgbe: ixgbe_dev_link_update_share() leaks memory and
memory mappings due to not cleaning up pthreads
Product: DPDK
Version: 20.02
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: martin.weiser@allegro-packets.com
Target Milestone: ---
In the patch "net/ixgbe: fix blocking system events"
(819d0d1d57f17aa40321648e99a50b49adc7bdf6) a thread is introduced to
run ixgbe_dev_setup_link_thread_handler().
Unfortunately this thread is not detached and just joined (the very
last one spawned that is) through ixgbe_dev_cancel_link_thread() upon
interface start/stop.
When an application repeatedly calls e.g. rte_eth_link_get_nowait() on
an ixgbe interface with no link this causes a lot of pthreads never to
be cleaned up.
Since each thread holds a mmap to the stack this can quite quickly
exhaust the allowed number of memory mappings for the process.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-04-09 17:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-447-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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 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.