Skip to contentSkip to conversation

rte_eth_rx_burst causes segmentation fault when encountered in a Secondary process

DPDK/examples Bug 1698 [email protected] 1 participant 2 messages Apr 24, 2025 – Jul 2

lore
Share & tools
lore
#0 lore raw

https://bugs.dpdk.org/show_bug.cgi?id=1698

Bug ID: 1698
Summary: rte_eth_rx_burst causes segmentation fault when
encountered in a Secondary process
Product: DPDK
Version: 23.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: examples
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---

Created attachment 311
--> https://bugs.dpdk.org/attachment.cgi?id=311&action=edit
This is the screenshot of the log that appears when the secondary process tries to execute tx_burst

I took a copy of the simple_mp main program from multi_process within the DPDK examples and modified it by adding bonding and allowing it to send dummy packets.

Two bonds are created, both are under the Active backup mode. This is done by the primary process.

Once the bonds are created, configured and started, the transmisssion of dummy packets starts. When tx_burst is run for the primary process, the transmission of packets occur without any issue.

However, when the tx_burst is encountered during the Secondary process with the primary process running in another terminal, a segmentation error occurs.

DPDK Version : 23.11

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
#1 lore raw

[DPDK/ethdev Bug 1698] bonding Rx crash in a secondary process

http://bugs.dpdk.org/show_bug.cgi?id=1698

Thomas Monjalon ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #6 from Thomas Monjalon ([email protected]) --- Resolved in https://dpdk.org/id/6d77d081d8
net/bonding: prevent crash on Rx/Tx from secondary process

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.