From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 880] [asan] mem: out of bound access in unit test
Date: Tue, 09 Nov 2021 19:47:08 +0000 [thread overview]
Message-ID: <bug-880-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=880
Bug ID: 880
Summary: [asan] mem: out of bound access in unit test
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: david.marchand@redhat.com
Target Milestone: ---
ASan reports:
18:08:02 DPDK_TEST=memory_autotest MALLOC_PERTURB_=143
/home/dmarchan/builds/build-gcc-static/app/test/dpdk-test
--file-prefix=memory_autotest -l 0-3
----------------------------------- output -----------------------------------
stdout:
RTE>>memory_autotest^M
stderr:
EAL: Detected CPU lcores: 28
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: WARNING! Base virtual address hint (0x100005000 != 0x7f695f22e000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: Multi-process socket /var/run/dpdk/memory_autotest/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: No available 2048 kB hugepages reported
EAL: WARNING! Base virtual address hint (0x10000b000 != 0x7f695efb2000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x100011000 != 0x7f695f201000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x240012000 != 0x7f6140000000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x280017000 != 0x7f695f200000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x3c0018000 != 0x7f5900000000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: Probe PCI driver: net_mlx4 (15b3:1007) device: 0000:04:00.0 (socket 0)
net_mlx4: cannot access device, is mlx4_ib loaded?
EAL: Requested device 0000:04:00.0 cannot be used
APP: HPET is not enabled, using TSC as default timer
=================================================================
==2495520==ERROR: AddressSanitizer: heap-buffer-overflow on address
0x7f617fe68cf0 at pc 0x000001eaa348 bp 0x7ffeb7ae11c0 sp 0x7ffeb7ae11b8
READ of size 1 at 0x7f617fe68cf0 thread T0
#0 0x1eaa347 in check_mem ../../dpdk/app/test/test_memory.c:36
#1 0x24cd50c in rte_memseg_walk_thread_unsafe
../../dpdk/lib/eal/common/eal_common_memory.c:729
#2 0x24cd55d in rte_memseg_walk
../../dpdk/lib/eal/common/eal_common_memory.c:745
#3 0x1eaa3ab in test_memory ../../dpdk/app/test/test_memory.c:94
#4 0x1ca5dcf in cmd_autotest_parsed ../../dpdk/app/test/commands.c:71
#5 0x2457d6d in cmdline_parse ../../dpdk/lib/cmdline/cmdline_parse.c:290
#6 0x245557f in cmdline_valid_buffer ../../dpdk/lib/cmdline/cmdline.c:26
#7 0x245d5cf in rdline_char_in ../../dpdk/lib/cmdline/cmdline_rdline.c:446
#8 0x245566b in cmdline_in ../../dpdk/lib/cmdline/cmdline.c:148
#9 0x245566b in cmdline_in ../../dpdk/lib/cmdline/cmdline.c:137
#10 0x40d93c in main ../../dpdk/app/test/test.c:214
#11 0x7f6962d5fb74 in __libc_start_main (/usr/lib64/libc.so.6+0x27b74)
#12 0x1ca5c9d in _start
(/home/dmarchan/builds/build-gcc-static/app/test/dpdk-test+0x1ca5c9d)
Address 0x7f617fe68cf0 is a wild pointer.
SUMMARY: AddressSanitizer: heap-buffer-overflow
../../dpdk/app/test/test_memory.c:36 in check_mem
Shadow bytes around the buggy address:
0x0fecaffc5140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fecaffc5150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fecaffc5160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fecaffc5170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fecaffc5180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0fecaffc5190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00[fa]fa
0x0fecaffc51a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fecaffc51b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fecaffc51c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fecaffc51d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fecaffc51e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==2495520==ABORTING
------------------------------------------------------------------------------
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-11-09 19:47 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-880-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.