DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Mingjin Ye <mingjinx.ye@intel.com>
Cc: <dev@dpdk.org>, <qiming.yang@intel.com>, <yidingx.zhou@intel.com>,
	"Wenjun Wu" <wenjun1.wu@intel.com>
Subject: Re: [PATCH] doc: add PMD known issue
Date: Thu, 20 Apr 2023 16:22:53 +0100	[thread overview]
Message-ID: <ZEFYzUGIYSbAkOw7@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20230420061429.140113-1-mingjinx.ye@intel.com>

On Thu, Apr 20, 2023 at 06:14:29AM +0000, Mingjin Ye wrote:
> 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..c346e377e2 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's 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.
> -- 

I disagree about this description of the bug. ASLR is not the problem;
instead driver is just not multi-process aware and uses the same pointers
in both primary and secondary processes. You will hit this issue even
without ASLR if primary and secondary processes use different static
binaries. Therefore, IMHO, title should be that the VF driver is not
multi-process safe, rather than pinning the blame on ASLR.

/Bruce

  parent reply	other threads:[~2023-04-20 15:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20  6:14 Mingjin Ye
2023-04-20 14:59 ` Stephen Hemminger
2023-04-20 15:22 ` Bruce Richardson [this message]
2023-05-06 10:02 ` [PATCH v2] " Mingjin Ye
2023-05-15  5:56   ` Zhang, Qi Z
2023-05-16 10:22   ` [PATCH v3] doc: comment VF does not support multi-process Mingjin Ye
2023-05-16 15:18     ` Stephen Hemminger
2023-05-17  2:29       ` Ye, MingjinX
2023-05-17 10:03     ` [PATCH v4] doc: update ixgbe VF features list Mingjin Ye
2023-05-18  8:25       ` Zhang, Qi Z
2023-04-20  6:43 [PATCH] doc: add PMD known issue Mingjin Ye

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=ZEFYzUGIYSbAkOw7@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mingjinx.ye@intel.com \
    --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).