From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/examples Bug 1751] [dpdk-25.07] multiprocess_symmetric_mp_packet: exiting the symmetric_mp example results in a core dump
Date: Mon, 21 Jul 2025 02:11:58 +0000 [thread overview]
Message-ID: <bug-1751-3-QkwdXrP2q6@https.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1751-3@https.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1751
Jiale Song (songx.jiale@intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Jiale Song (songx.jiale@intel.com) ---
Offending commit has been reverted in main tree for 25.07 release.
fix patch:
http://patchwork.dpdk.org/project/dpdk/patch/20250715121111.156639-1-thomas@monjalon.net/
the patch merged into dpdk main branch.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2970 bytes --]
prev parent reply other threads:[~2025-07-21 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 5:33 [DPDK/examples Bug 1751] [dpdk24.07] multiprocess_symmetric_mp_packet: exiting the symmetric_mp example results in a core dump bugzilla
2025-07-21 2:11 ` bugzilla [this message]
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-QkwdXrP2q6@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.