From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/examples Bug 1714] symmetric_mp termination failure with ASan (detected memory leaks)
Date: Tue, 27 May 2025 16:03:10 +0000 [thread overview]
Message-ID: <bug-1714-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3932 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1714
Bug ID: 1714
Summary: symmetric_mp termination failure with ASan (detected
memory leaks)
Product: DPDK
Version: 25.03
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: sbadawi@nvidia.com
Target Milestone: ---
Created attachment 318
--> https://bugs.dpdk.org/attachment.cgi?id=318&action=edit
leakSanitizer_trace
$ ./build/examples/dpdk-symmetric_mp -n 4 -a 0000:08:00.0 -a 0000:08:00.1 -l 1
--proc-type=primary -- -p 0x3 --num-procs=8 --proc-id=0
EAL: Detected CPU lcores: 10
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: VFIO support initialized
# Initialising port 0... # Initialising port 1...
Checking link statusdone
Port 0 Link up at 100 Gbps FDX Autoneg
Port 1 Link up at 100 Gbps FDX Autoneg
APP: Finished Process Init.
Lcore 1 using ports 0 1
lcore 1 using queue 0 of each port
^C
Exiting on signal 2
Port 0: RX - 0, TX - 0, Drop - 0
Port 1: RX - 0, TX - 0, Drop - 0
=================================================================
==1279169==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 11424 byte(s) in 14 object(s) allocated from:
#0 0x7f4e90f67a37 in __interceptor_calloc
../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154
#1 0x557c8add30a0 in mlx5_malloc
(./build/examples/dpdk-symmetric_mp+0xd140a0)
#2 0x557c8b695525 in mlx5dr_action_template_create
(./build/examples/dpdk-symmetric_mp+0x15d6525)
#3 0x557c8b58e03a in __flow_hw_actions_template_create
(./build/examples/dpdk-symmetric_mp+0x14cf03a)
#4 0x557c8b58f6ec in flow_hw_create_ctrl_rx_rss_template
(./build/examples/dpdk-symmetric_mp+0x14d06ec)
#5 0x557c8b5e3529 in mlx5_flow_hw_ctrl_flows
(./build/examples/dpdk-symmetric_mp+0x1524529)
#6 0x557c8afcbde1 in mlx5_traffic_enable
(./build/examples/dpdk-symmetric_mp+0xf0cde1)
#7 0x557c8a33e163 in mlx5_dev_start.cold
(./build/examples/dpdk-symmetric_mp+0x27f163)
#8 0x557c8abb48e4 in rte_eth_dev_start
(./build/examples/dpdk-symmetric_mp+0xaf58e4)
#9 0x557c8a3e0aa4 in smp_port_init
(./build/examples/dpdk-symmetric_mp+0x321aa4)
#10 0x557c8a3cb24f in main (./build/examples/dpdk-symmetric_mp+0x30c24f)
#11 0x7f4e90639d8f in __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
Direct leak of 8960 byte(s) in 140 object(s) allocated from:
#0 0x7f4e90f67a37 in __interceptor_calloc
../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154
#1 0x557c8add30a0 in mlx5_malloc
(./build/examples/dpdk-symmetric_mp+0xd140a0)
#2 0x557c8b6686c0 in mlx5dr_match_template_create
(./build/examples/dpdk-symmetric_mp+0x15a96c0)
#3 0x557c8b5938de in flow_hw_pattern_template_create
(./build/examples/dpdk-symmetric_mp+0x14d48de)
#4 0x557c8b59c156 in __flow_hw_configure
(./build/examples/dpdk-symmetric_mp+0x14dd156)
#5 0x557c8b5a4f0f in flow_hw_init
(./build/examples/dpdk-symmetric_mp+0x14e5f0f)
#6 0x557c8a33b2ed in mlx5_dev_start.cold
(./build/examples/dpdk-symmetric_mp+0x27c2ed)
#7 0x557c8abb48e4 in rte_eth_dev_start
(./build/examples/dpdk-symmetric_mp+0xaf58e4)
#8 0x557c8a3e0aa4 in smp_port_init
(./build/examples/dpdk-symmetric_mp+0x321aa4)
#9 0x557c8a3cb24f in main (./build/examples/dpdk-symmetric_mp+0x30c24f)
#10 0x7f4e90639d8f in __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
[..]
Environment info:
OS: Ubuntu22.04 (x86_64)
Kernel: 5.15.0-25-generic
Device: ConnectX-6 DX
gcc: 11.2.0
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5936 bytes --]
reply other threads:[~2025-05-27 16:03 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-1714-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.