From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1271] Using dumpcap to capture packets with multiple pmds and enable mbuf check can lead to dpdk proc core
Date: Wed, 02 Aug 2023 15:06:51 +0000 [thread overview]
Message-ID: <bug-1271-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1271
Bug ID: 1271
Summary: Using dumpcap to capture packets with multiple pmds
and enable mbuf check can lead to dpdk proc core
Product: DPDK
Version: 23.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: sunshaowei01@baidu.com
Target Milestone: ---
When creating a mempool, dumpcap selects the type 'mp_sc' causes thread
insecurity when multiple PMDs in the main process apply for mbuf. If the check
of mbuf is enabled at this time, it will cause the process to panic. So, the
type for creating mempool should be 'mp_mc'
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2800 bytes --]
next reply other threads:[~2023-08-02 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 15:06 bugzilla [this message]
2023-11-28 16:25 ` bugzilla
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-1271-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;
as well as URLs for NNTP newsgroup(s).