patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Ye, MingjinX" <mingjinx.ye@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Zhou, YidingX" <yidingx.zhou@intel.com>,
	"Ye, MingjinX" <mingjinx.ye@intel.com>,
	"Wu, Wenjun1" <wenjun1.wu@intel.com>
Subject: RE: [PATCH v2] doc: add PMD known issue
Date: Mon, 15 May 2023 05:56:47 +0000	[thread overview]
Message-ID: <DM4PR11MB5994D5EBB1D44CB37E84248DD7789@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230506100252.215680-1-mingjinx.ye@intel.com>



> -----Original Message-----
> From: Mingjin Ye <mingjinx.ye@intel.com>
> Sent: Saturday, May 6, 2023 6:03 PM
> To: dev@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>; stable@dpdk.org; Zhou, YidingX
> <yidingx.zhou@intel.com>; Ye, MingjinX <mingjinx.ye@intel.com>; Wu,
> Wenjun1 <wenjun1.wu@intel.com>
> Subject: [PATCH v2] doc: add PMD known issue
> 
> Add a known issue: The ixgbe_vf driver is not multi-process safe.
> 
> Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
> ---
> v2: Modify issue description reason.
> ---
>  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..9fb3c39bf4 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)
> +
> +VF driver is not multi-process safe
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +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.

Which function did we encounter the issue with? Is this a bug in the PMD? In a multi-process scenario, we should not assume that the addresses of functions are identical across different processes. Additionally, this issue should not be related ASLR because the primary and secondary processes could be two different applications but still share the same DPDK library.

> +
> +   .. 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


  reply	other threads:[~2023-05-15  5:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230420061429.140113-1-mingjinx.ye@intel.com>
2023-05-06 10:02 ` Mingjin Ye
2023-05-15  5:56   ` Zhang, Qi Z [this message]
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

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=DM4PR11MB5994D5EBB1D44CB37E84248DD7789@DM4PR11MB5994.namprd11.prod.outlook.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=mingjinx.ye@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=stable@dpdk.org \
    --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).