From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1255] [asan] net/mlx5: memory leak on port cleanup
Date: Tue, 20 Jun 2023 11:09:48 +0000 [thread overview]
Message-ID: <bug-1255-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3205 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1255
Bug ID: 1255
Summary: [asan] net/mlx5: memory leak on port cleanup
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: david.marchand@redhat.com
Target Milestone: ---
This is something I caught on RHEL 9.2 but it might be generic:
# rm -rf build; meson setup build
-Denable_drivers=bus/auxiliary,common/mlx5,net/mlx5 -Ddisable_libs=*
-Denable_apps=test-pmd -Dbuildtype=debug -Ddeveloper_mode=disabled
-Db_sanitize=address -Dtests=false -Dexamples=
...
# ninja -C build
...
# lspci | grep Ethernet.*Mellanox
98:00.0 Ethernet controller: Mellanox Technologies MT2892 Family [ConnectX-6
Dx]
98:00.1 Ethernet controller: Mellanox Technologies MT2892 Family [ConnectX-6
Dx]
98:00.2 Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen
Virtual Function
98:01.2 Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen
Virtual Function
# echo quit | ASAN_OPTIONS="use_sigaltstack=0" ./build/app/dpdk-testpmd -a
0000:98:00.0 -- -ia
...
=================================================================
==135295==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 80 byte(s) in 1 object(s) allocated from:
#0 0x7f14054b4bd7 in calloc (/lib64/libasan.so.6+0xb4bd7)
#1 0x7f1405e5ec6c in dr_action_create_generic
../providers/mlx5/dr_action.c:1009
#2 0x294135e in mlx5_flow_os_create_flow_action_dest_devx_tir
../drivers/net/mlx5/linux/mlx5_flow_os.h:409
#3 0x294b3e7 in mlx5_devx_hrxq_new ../drivers/net/mlx5/mlx5_devx.c:924
#4 0x294cb13 in mlx5_devx_drop_action_create
../drivers/net/mlx5/mlx5_devx.c:1169
#5 0xec0f50 in mlx5_drop_action_create ../drivers/net/mlx5/mlx5_rxq.c:3101
#6 0x2c62d99 in mlx5_dev_spawn ../drivers/net/mlx5/linux/mlx5_os.c:1556
#7 0x2c68fb2 in mlx5_os_pci_probe_pf
../drivers/net/mlx5/linux/mlx5_os.c:2348
#8 0x2c6a4b1 in mlx5_os_pci_probe ../drivers/net/mlx5/linux/mlx5_os.c:2497
#9 0x2c6b08e in mlx5_os_net_probe ../drivers/net/mlx5/linux/mlx5_os.c:2578
#10 0xc6afff in drivers_probe ../drivers/common/mlx5/mlx5_common.c:937
#11 0xc6b6a6 in mlx5_common_dev_probe
../drivers/common/mlx5/mlx5_common.c:1027
#12 0xc8ad0a in mlx5_common_pci_probe
../drivers/common/mlx5/mlx5_common_pci.c:168
#13 0xc1e3fa in rte_pci_probe_one_driver
../drivers/bus/pci/pci_common.c:312
#14 0xc1eadb in pci_probe_all_drivers ../drivers/bus/pci/pci_common.c:396
#15 0xc1eb82 in pci_probe ../drivers/bus/pci/pci_common.c:423
#16 0xb72d22 in rte_bus_probe ../lib/eal/common/eal_common_bus.c:78
#17 0xbe317e in rte_eal_init ../lib/eal/linux/eal.c:1300
#18 0x5e80a0 in main ../app/test-pmd/testpmd.c:4515
#19 0x7f140503feaf in __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
SUMMARY: AddressSanitizer: 80 byte(s) leaked in 1 allocation(s).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5087 bytes --]
next reply other threads:[~2023-06-20 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 11:09 bugzilla [this message]
2023-06-21 19:11 ` Asaf Penso
2023-06-23 8:55 ` 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=bug-1255-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 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).