From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4155143CB2; Thu, 14 Mar 2024 10:26:05 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 02F5142DD9; Thu, 14 Mar 2024 10:26:05 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id B509A40297 for ; Thu, 14 Mar 2024 10:26:03 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id A5FB443CB3; Thu, 14 Mar 2024 10:26:03 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [DPDK/examples Bug 1401] [dpdk-24.03][asan] cbdma: ERROR: AddressSanitizer: SEGV on unknown address in rte_rwlock_write_lock when launch dpdk-dma Date: Thu, 14 Mar 2024 09:26:03 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: examples X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: yux.jiang@intel.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17104083630.Afbd05a0.4182268 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17104083630.Afbd05a0.4182268 Date: Thu, 14 Mar 2024 10:26:03 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1401 Bug ID: 1401 Summary: [dpdk-24.03][asan] cbdma: ERROR: AddressSanitizer: SEGV on unknown address in rte_rwlock_write_lock when launch dpdk-dma Product: DPDK Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: examples Assignee: dev@dpdk.org Reporter: yux.jiang@intel.com Target Milestone: --- [Environment] DPDK version:=20 a86f381b82 (HEAD -> main, tag: v24.03-rc2, origin/main, origin/HEAD) versio= n: 24.03-rc2 Other software versions: name/version for QEMU, OVS, etc. Repeat as require= d. OS: Ubuntu 22.04.3 LTS/5.15.0-92-generic Compiler: gcc version 11.4.0 Hardware platform: Intel(R) Xeon(R) Platinum 8380 CPU @ 2.30GHz [Test Setup] Steps to reproduce List the steps to reproduce the issue. 1, Build app and set randomize_va_space=3D0 rm -fr x86_64-native-linuxapp-gcc/ CC=3Dgcc meson -Denable_kmods=3DTrue -Dlibdir=3Dlib -Dbuildtype=3Ddebug -Db_lundef=3Dfalse -Db_sanitize=3Daddress --default-library=3Dstatic x86_64-native-linuxapp-gcc meson configure -Dexamples=3Ddma x86_64-native-linuxapp-gcc ninja -C x86_64-native-linuxapp-gcc echo 0 > /proc/sys/kernel/randomize_va_space 2, Bind dma to vfio-pci ./usertools/dpdk-devbind.py --force --bind=3Dvfio-pci 0000:00:01.0 0000:00:= 01.1 0000:00:01.2 0000:00:01.3 3, Launch primary app x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 5-6 -n 8 -a 0000:00:01.0 -a 0000:00:01.1 -a 0000:00:01.2 -a 0000:00:01.3=20 --file-prefix=3Ddpdk_2693680_20240314155440 --vdev net_null_0 --proc-type=3Dprimary -- -i testpmd> port stop all 4, Launch secondary app: dpdk-dma x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 5-7 -n 8 -a 0000:00:01.0 -a 0000:00:01.1 -a 0000:00:01.2 -a 0000:00:01.3=20 --file-prefix=3Ddpdk_2693680_20240314155440 --proc-type=3Dsecondary --= vdev net_null_0 -- -p 0x1 -q 4 --no-mac-updating -c hw Show the output from the previous commands: EAL: Detected CPU lcores: 80 EAL: Detected NUMA nodes: 2 EAL: Detected static linkage of DPDK EAL: Cannot mmap memory for rte_config at [0x7ffff4007000], got [0x7ffff3dc9000] - please use '--base-virtaddr' option EAL: FATAL: Cannot init config EAL: Cannot init config EAL: Error - exiting with code: 1 Cause: Invalid EAL arguments AddressSanitizer:DEADLYSIGNAL =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D2802374=3D=3DERROR: AddressSanitizer: SEGV on unknown address 0x7ffff= 3dc9024 (pc 0x555556ba5798 bp 0x7fffffffde90 sp 0x7fffffffde00 T0) =3D=3D2802374=3D=3DThe signal is caused by a READ memory access. #0 0x555556ba5798 in rte_rwlock_write_lock ../lib/eal/include/generic/rte_rwlock.h:209 #1 0x555556ba9a82 in rte_eal_memory_detach ../lib/eal/common/eal_common_memory.c:1029 #2 0x555556c04fb5 in rte_eal_cleanup ../lib/eal/linux/eal.c:1379 #3 0x555556b8f610 in rte_exit ../lib/eal/common/eal_common_debug.c:46 #4 0x555555ec144b in main ../examples/dma/dmafwd.c:1021 #5 0x7ffff7225d8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 #6 0x7ffff7225e3f in __libc_start_main_impl ../csu/libc-start.c:392 #7 0x555555e89074 in _start (/root/dpdk/x86_64-native-linuxapp-gcc/examples/dpdk-dma+0x935074) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV ../lib/eal/include/generic/rte_rwlock.h:209= in rte_rwlock_write_lock =3D=3D2802374=3D=3DABORTING [Expected Result] Launch app successfully and no Asan error [Regression] Is this issue a regression: (Y/N) Y Version the regression was introduced: (Need https://bugs.dpdk.org/show_bug.cgi?id=3D1387's patch) commit 52c386779fcd9f31708f1491961637c31f6bcb61 (HEAD -> 52c386779f) Author: Damodharam Ammepalli Date: Wed Sep 20 13:27:17 2023 -0700 net/bnxt: support 400G speed for P7 devices P7 devices report speeds over speeds2 hsi fields. Adding required support to capture the capability from phy_qcap and save the speeds2 fields into driver priv structure. In fixed mode update the link_speed from force_link_speeds2 field. Updates to logging to provide more info regarding numbers of lanes and the link signal mode. Some code refactoring done for PHY auto detect and displaying XCVR information. Signed-off-by: Damodharam Ammepalli Reviewed-by: Ajit Khaparde if don't set echo 0 > /proc/sys/kernel/randomize_va_space, this error disappears --=20 You are receiving this mail because: You are the assignee for the bug.= --17104083630.Afbd05a0.4182268 Date: Thu, 14 Mar 2024 10:26:03 +0100 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1401
Summary [dpdk-24.03][asan] cbdma: ERROR: AddressSanitizer: SEGV on un= known address in rte_rwlock_write_lock when launch dpdk-dma
Product DPDK
Version unspecified
Hardware All
OS All
Status UNCONFIRMED
Severity normal
Priority Normal
Component examples
Assignee dev@dpdk.org
Reporter yux.jiang@intel.com
Target Milestone --- 

[Environment]
DPDK version:=20
a86f381b82 (HEAD -> main, tag: v24.03-rc2, origin/main, origin/HEAD) ver=
sion:
24.03-rc2
Other software versions: name/version for QEMU, OVS, etc. Repeat as require=
d.
OS: Ubuntu 22.04.3 LTS/5.15.0-92-generic
Compiler: gcc version 11.4.0
Hardware platform: Intel(R) Xeon(R) Platinum 8380 CPU @ 2.30GHz

[Test Setup]
Steps to reproduce
List the steps to reproduce the issue.

1, Build app and set randomize_va_space=3D0
rm -fr x86_64-native-linuxapp-gcc/
CC=3Dgcc meson -Denable_kmods=3DTrue -Dlibdir=3Dlib  -Dbuildtype=3Ddebug
-Db_lundef=3Dfalse -Db_sanitize=3Daddress --default-library=3Dstatic
x86_64-native-linuxapp-gcc
meson configure -Dexamples=3Ddma x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc

echo 0 > /proc/sys/kernel/randomize_va_space


2, Bind dma to vfio-pci
./usertools/dpdk-devbind.py --force --bind=3Dvfio-pci 0000:00:01.0 0000:00:=
01.1
0000:00:01.2 0000:00:01.3

3, Launch primary app
x86_64-native-linuxapp-gcc/app/dpdk-testpmd  -l 5-6 -n 8 -a 0000:00:01.0 -a
0000:00:01.1 -a 0000:00:01.2 -a 0000:00:01.3=20
--file-prefix=3Ddpdk_2693680_20240314155440  --vdev net_null_0
--proc-type=3Dprimary  -- -i
testpmd> port stop all

4, Launch secondary app: dpdk-dma
x86_64-native-linuxapp-gcc/examples/dpdk-dma  -l 5-7 -n 8 -a 0000:00:01.0 -a
0000:00:01.1 -a 0000:00:01.2 -a 0000:00:01.3=20
--file-prefix=3Ddpdk_2693680_20240314155440      --proc-type=3Dsecondary --=
vdev
net_null_0 -- -p 0x1 -q 4 --no-mac-updating -c hw


Show the output from the previous commands:
EAL: Detected CPU lcores: 80
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Cannot mmap memory for rte_config at [0x7ffff4007000], got
[0x7ffff3dc9000] - please use '--base-virtaddr' option
EAL: FATAL: Cannot init config
EAL: Cannot init config
EAL: Error - exiting with code: 1
  Cause: Invalid EAL arguments
AddressSanitizer:DEADLYSIGNAL
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D2802374=3D=3DERROR: AddressSanitizer: SEGV on unknown address 0x7ffff=
3dc9024 (pc
0x555556ba5798 bp 0x7fffffffde90 sp 0x7fffffffde00 T0)
=3D=3D2802374=3D=3DThe signal is caused by a READ memory access.
    #0 0x555556ba5798 in rte_rwlock_write_lock
../lib/eal/include/generic/rte_rwlock.h:209
    #1 0x555556ba9a82 in rte_eal_memory_detach
../lib/eal/common/eal_common_memory.c:1029
    #2 0x555556c04fb5 in rte_eal_cleanup ../lib/eal/linux/eal.c:1379
    #3 0x555556b8f610 in rte_exit ../lib/eal/common/eal_common_debug.c:46
    #4 0x555555ec144b in main ../examples/dma/dmafwd.c:1021
    #5 0x7ffff7225d8f in __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
    #6 0x7ffff7225e3f in __libc_start_main_impl ../csu/libc-start.c:392
    #7 0x555555e89074 in _start
(/root/dpdk/x86_64-native-linuxapp-gcc/examples/dpdk-dma+0x935074)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV ../lib/eal/include/generic/rte_rwlock.h:209=
 in
rte_rwlock_write_lock
=3D=3D2802374=3D=3DABORTING


[Expected Result]
Launch app successfully and no Asan error


[Regression]
Is this issue a regression: (Y/N) Y

Version the regression was introduced: (Need
https://bugs.dpdk.org/show_bug.cgi?id=3D1387's patch)
commit 52c386779fcd9f31708f1491961637c31f6bcb61 (HEAD -> 52c386779f)
Author: Damodharam Ammepalli <damodharam.ammepalli@broadcom.com>
Date:   Wed Sep 20 13:27:17 2023 -0700

    net/bnxt: support 400G speed for P7 devices

    P7 devices report speeds over speeds2 hsi fields. Adding required
    support to capture the capability from phy_qcap and save the
    speeds2 fields into driver priv structure.
    In fixed mode update the link_speed from force_link_speeds2 field.
    Updates to logging to provide more info regarding numbers of lanes
    and the link signal mode.

    Some code refactoring done for PHY auto detect and displaying
    XCVR information.

    Signed-off-by: Damodharam Ammepalli <damodharam.ammepalli@broadcom.com>
    Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>

if don't set echo 0 > /proc/sys/kernel/randomize_va_space, this error
disappears

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17104083630.Afbd05a0.4182268--