From: Mingjin Ye <mingjinx.ye@intel.com>
To: dev@dpdk.org
Cc: yidingx.zhou@intel.com, Mingjin Ye <mingjinx.ye@intel.com>,
Qiming Yang <qiming.yang@intel.com>,
Wenjun Wu <wenjun1.wu@intel.com>
Subject: [PATCH] doc: add PMD known issue
Date: Thu, 20 Apr 2023 06:43:36 +0000 [thread overview]
Message-ID: <20230420064336.141247-1-mingjinx.ye@intel.com> (raw)
Add a known issue: ASLR feature causes core dump.
Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
---
doc/guides/nics/ixgbe.rst | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst
index b1d77ab7ab..459d0d8380 100644
--- a/doc/guides/nics/ixgbe.rst
+++ b/doc/guides/nics/ixgbe.rst
@@ -461,3 +461,18 @@ show bypass config
Show the bypass configuration for a bypass enabled NIC using the lowest port on the NIC::
testpmd> show bypass config (port_id)
+
+ASLR feature causes core dump
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Core dump may occur when we start secondary processes on the vf port.
+Mainstream Linux distributions have the ASLR feature enabled by default,
+and the text segment of the process memory space is randomized.
+The secondary process calls the function address shared by the primary
+process, resulting in a core dump.
+
+ .. Note::
+
+ Support for ASLR features varies by distribution. Redhat and
+ Centos series distributions work fine. Ubuntu distributions
+ will core dump, other Linux distributions are unknown.
--
2.25.1
next reply other threads:[~2023-04-20 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 6:43 Mingjin Ye [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-20 6:14 Mingjin Ye
2023-04-20 14:59 ` Stephen Hemminger
2023-04-20 15:22 ` Bruce Richardson
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=20230420064336.141247-1-mingjinx.ye@intel.com \
--to=mingjinx.ye@intel.com \
--cc=dev@dpdk.org \
--cc=qiming.yang@intel.com \
--cc=wenjun1.wu@intel.com \
--cc=yidingx.zhou@intel.com \
/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).