From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/examples Bug 1751] [dpdk24.07] multiprocess_symmetric_mp_packet: exiting the symmetric_mp example results in a core dump
Date: Fri, 11 Jul 2025 05:33:08 +0000 [thread overview]
Message-ID: <bug-1751-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3534 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1751
Bug ID: 1751
Summary: [dpdk24.07] multiprocess_symmetric_mp_packet: exiting
the symmetric_mp example results in a core dump
Product: DPDK
Version: 25.03
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: songx.jiale@intel.com
Target Milestone: ---
Environment
===========
DPDK version: 9fe9c0b231c8da5435bfccb1963121b4277f961c version: dpdk25.07-rc3
OS: Ubuntu 24.04.2 LTS/6.8.0-60-generic
Compiler: gcc version 13.3.0
Hardware platform: Intel(R) Xeon(R) Platinum 8380 CPU @ 2.30GHz
NIC hardware: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection
[8086:10fb] (rev 01)
NIC firmware:
driver: vfio-pci
kdriver: ixgbe-6.1.5
firmware-version: 0x000161bf
Test Setup
Steps to reproduce
==================
1. compile dpdk
rm -rf x86_64-native-linuxapp-gcc
CC=gcc meson -Denable_kmods=False -Dlibdir=lib
-Dexamples='multi_process/symmetric_mp' --default-library=static
x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
2. bind port to vfio-pci
./usertools/dpdk-devbind.py -b vfio-pci 0000:b1:00.0 0000:b1:00.1
3. start testpmd
the first process:
x86_64-native-linuxapp-gcc/examples/dpdk-symmetric_mp -l 1 -n 4 -a 0000:b1:00.0
-a 0000:b1:00.1 --file-prefix=dpdk_3722445_20250711093937 --proc-type=auto
-- -p 0x3 --num-procs=2 --proc-id=0
the secondary process:
x86_64-native-linuxapp-gcc/examples/dpdk-symmetric_mp -l 2 -n 4 -a 0000:b1:00.0
-a 0000:b1:00.1 --file-prefix=dpdk_3722445_20250711093937 --proc-type=auto
-- -p 0x3 --num-procs=2 --proc-id=1
4. exit the first process
^C
Results:
========
^C
the first process: Exiting on signal 2Port 0: RX - 0, TX - 1, Drop - 0
Port 1: RX - 1, TX - 0, Drop - 0
APP: Close ports.
EAL: Error - exiting with code: 1
Error closing ports
EAL: failed to send to
(/var/run/dpdk/dpdk_3722445_20250711093937/mp_socket_794973_148a6526e3624d) due
to Bad file descriptor
EAL: Fail to send request
/var/run/dpdk/dpdk_3722445_20250711093937/mp_socket_794973_148a6526e3624d:mp_malloc_sync
EAL: Could not send sync request to secondary process
the secondary process:
EAL: Detected CPU lcores: 80
EAL: Detected NUMA nodes: 2
EAL: Auto-detected process type: SECONDARY
EAL: Detected static linkage of DPDK
EAL: Multi-process socket
/var/run/dpdk/dpdk_3722445_20250711093937/mp_socket_794279_148a2f16b62b59
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
EAL: Using IOMMU type 1 (Type 1)
APP: Finished Process Init.
Lcore 2 using ports 0 1
lcore 2 using queue 1 of each port
Segmentation fault (core dumped)
Expected Result:
================
exit the symmetric_mp example normally.
bad commit:
===========
commit 4382d58097b41d1e1229ce5fc2943994bf44bd83
Author: Maayan Kashani <mkashani@nvidia.com>
Date: Tue Jul 8 10:09:54 2025 +0300
examples/multi_process: fix ports cleanup on exit
Device was started but not stopped on exit signal.
Added port stop and close on exit.
Fixes: af75078fece3 ("first public release")
Cc: stable@dpdk.org
Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5672 bytes --]
reply other threads:[~2025-07-11 5:33 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-1751-3@https.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).