From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 454C142A7C; Sat, 6 May 2023 12:09:32 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D78E740DFD; Sat, 6 May 2023 12:09:31 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mails.dpdk.org (Postfix) with ESMTP id 29CA1406B8; Sat, 6 May 2023 12:09:29 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1683367770; x=1714903770; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=fTZu6ohbKXjcmCjeeWJtjld7DX/wtbU9rZ5jqAcHG88=; b=P+rjk1NvYtmNXzW2B+TDA0VDddAW1LSbEDwxl45+rqLV501VTZEgPUzr o5UdDiToU0+UUA5HsxQsUvGPlaRGkcYilUTQtT2hg4otwnlUL3dt5TBVt d0GnT9rq6PpF/0D9kls612eySjoxeHSnEhDNFdlR9SBeo3d2yQ0QLvq8e 1e9wMmyqwTHU9W1wS1LmhssgsSFdGVmBUwUm1hvEIRrlG6xylcPDleV54 ZVFKokAIxO1cQnywJXe9edkwdemvHnfx7SR69sqwJ5c9T1rQMf314Pg8T 7/s9lZZViHV1ecHbWyggU80Z6MPNcPoe0y9sO9Y8ZoGZow7M4YovZYVu+ A==; X-IronPort-AV: E=McAfee;i="6600,9927,10701"; a="333798873" X-IronPort-AV: E=Sophos;i="5.99,254,1677571200"; d="scan'208";a="333798873" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 May 2023 03:09:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10701"; a="1027832980" X-IronPort-AV: E=Sophos;i="5.99,254,1677571200"; d="scan'208";a="1027832980" Received: from unknown (HELO localhost.localdomain) ([10.239.252.253]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 May 2023 03:09:26 -0700 From: Mingjin Ye To: dev@dpdk.org Cc: qiming.yang@intel.com, stable@dpdk.org, yidingx.zhou@intel.com, Mingjin Ye , Wenjun Wu Subject: [PATCH v2] doc: add PMD known issue Date: Sat, 6 May 2023 10:02:52 +0000 Message-Id: <20230506100252.215680-1-mingjinx.ye@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20230420061429.140113-1-mingjinx.ye@intel.com> References: <20230420061429.140113-1-mingjinx.ye@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Add a known issue: The ixgbe_vf driver is not multi-process safe. Signed-off-by: Mingjin Ye --- 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. + + .. 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