Primary shutdown not caught by all secondaries

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

            Bug ID: 1942
           Summary: Primary shutdown not caught by all secondaries
           Product: DPDK
           Version: 26.03
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: [email protected]
          Reporter: [email protected]

Target Milestone: ---

The fix to send message when primary exits was wrong approach. It doesn't work with other applications like dumpcap, pdump or customer applications.

This is shown by:
- run test pmd
- start dpdk dump (secondary)
- exit test pmd
The shutdown process hangs and eventually times out.

Primary: Sending 'stop_req' request to secondary...
EAL: Fail to recv reply for request /var/run/dpdk/rte/mp_socket_130405_3692c058749:mp_testpmd

Stopping port 0...
Stopping ports...
Done

Shutting down port 0...
Closing ports...
Port 0 is closed
Done

And in dumpcap:

# ./build/app/dpdk-dumpcap
File: /tmp/dpdk-dumpcap_0_net_tap0_20260506195857.pcapng
Capturing on 'net_tap0'
Packets captured: 29 EAL: Cannot find action: mp_testpmd
Primary process is no longer active, exiting...

Testpmd should not assume secondary is testpmd!

You are receiving this mail because:
You are the assignee for the bug.