From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 735] [asan] driver bonding has memory leak
Date: Wed, 16 Jun 2021 03:09:45 +0000 [thread overview]
Message-ID: <bug-735-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=735
Bug ID: 735
Summary: [asan] driver bonding has memory leak
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: zhihongx.peng@intel.com
Target Milestone: ---
Created attachment 159
--> https://bugs.dpdk.org/attachment.cgi?id=159&action=edit
asan patch
Environment
dpdk: 21.05
test patch: 0007-porting-AddressSanitizer-feature-to-DPDK.patch
0001-Solve-gcc-compile-dpdk-asan.patch 0001-Solve-known-bugs.patch
Test Setup:
1. git apply 0007-porting-AddressSanitizer-feature-to-DPDK.patch
2. git apply 0001-Solve-gcc-compile-dpdk-asan.patch
3. git apply 0001-Solve-known-bugs.patch
4. CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib -Dbuildtype=debug
-Db_lundef=false -Db_sanitize=address --default-library=static
x86_64-native-linuxapp-gc
5. ninja -C x86_64-native-linuxapp-gcc -j 110
6. ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l
1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51
,52,53 -n 4 -a 0000:18:00.0 -a 0000:18:00.1
--file-prefix=dpdk_12870_20210616013323 --vdev
'net_bonding0,slave=0000:18:00.0,slave=0000:18:00.1,mode=4,agg_mode=bandwidth'
– -i
7. expect result
Start up normally
actual result
There are some errors here:
==311201==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 528 byte(s) in 1 object(s) allocated from:
#0 0x7f2f98331ba8 in __interceptor_malloc (/lib64/libasan.so.5+0xefba8)
#1 0x10d7c6a in rte_kvargs_parse ../lib/kvargs/rte_kvargs.c:232
#2 0x190d682 in bond_probe ../drivers/net/bonding/rte_eth_bond_pmd.c:3361
#3 0x1184b20 in vdev_probe_all_drivers ../drivers/bus/vdev/vdev.c:211
#4 0x118693a in vdev_probe ../drivers/bus/vdev/vdev.c:558
#5 0x103ec0e in rte_bus_probe ../lib/eal/common/eal_common_bus.c:79
#6 0x10a0dd8 in rte_eal_init ../lib/eal/linux/eal.c:1286
#7 0x6e9dce in main ../app/test-pmd/testpmd.c:3752
#8 0x7f2f96c64492 in __libc_start_main (/lib64/libc.so.6+0x23492)
Indirect leak of 64 byte(s) in 1 object(s) allocated from:
#0 0x7f2f9827dda0 in strdup (/lib64/libasan.so.5+0x3bda0)
#1 0x10d74d0 in rte_kvargs_tokenize ../lib/kvargs/rte_kvargs.c:35
#2 0x10d7ca5 in rte_kvargs_parse ../lib/kvargs/rte_kvargs.c:237
#3 0x190d682 in bond_probe ../drivers/net/bonding/rte_eth_bond_pmd.c:3361
#4 0x1184b20 in vdev_probe_all_drivers ../drivers/bus/vdev/vdev.c:211
#5 0x118693a in vdev_probe ../drivers/bus/vdev/vdev.c:558
#6 0x103ec0e in rte_bus_probe ../lib/eal/common/eal_common_bus.c:79
#7 0x10a0dd8 in rte_eal_init ../lib/eal/linux/eal.c:1286
#8 0x6e9dce in main ../app/test-pmd/testpmd.c:3752
#9 0x7f2f96c64492 in __libc_start_main (/lib64/libc.so.6+0x23492)
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-06-16 3:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 3:09 bugzilla [this message]
2021-10-12 7:45 ` bugzilla
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-735-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).