DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1942] Primary shutdown not caught by all secondaries
Date: Thu, 07 May 2026 03:12:18 +0000	[thread overview]
Message-ID: <bug-1942-3@http.bugs.dpdk.org/> (raw)

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: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  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.

                 reply	other threads:[~2026-05-07  3:12 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-1942-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox