From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1073] The `rte_mempool_ops_table` is process unsafe
Date: Thu, 01 Sep 2022 11:30:27 +0000 [thread overview]
Message-ID: <bug-1073-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1073
Bug ID: 1073
Summary: The `rte_mempool_ops_table` is process unsafe
Product: DPDK
Version: 19.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: wdy_s@foxmail.com
Target Milestone: ---
Created attachment 219
--> https://bugs.dpdk.org/attachment.cgi?id=219&action=edit
GDB print value corresponding to the table（rte_mempool_ops_table）（myapp and
dpdk-pdump）
The `rte_mempool_ops_table` is process unsafe!
When a process is started, the table (rte_mempool_ops_table) will be
initialized with a macro (rte_mempool.h:MEMPOOL_REGISTER_OPS). However,
different process initialization will cause inconsistent index values
(ops_index) (such as myapp and dpdk pdump). After the initialization memory
pool is created in the dpdk pdump process, mp->ops_index = 0, mp->ops_index=2
in myapp。 Different processes using the shared memory pool will be coredump
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-09-01 11:30 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-1073-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 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.