From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 5577F10A3 for ; Thu, 17 Jan 2019 17:34:06 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 08B50152F; Thu, 17 Jan 2019 11:34:04 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 17 Jan 2019 11:34:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=/e6/6EUpmy8KU5oHHLsX64Tyd5jqOt575prpOrtJPD4=; b=a99OmH8DEAhM wuCsZyNLv20Xm/OKCrEwqEZh80mXZPFxHqjWN6quAOmzYTqBdCZoCsHj3y+FvrQL fMXFPuIHShkliu3cLUbdL9lq3VxuglGKZkuidQaCTPhfiCj0uWLckLeLQRFQYdA2 2FklAZ44NYydAK96fPoPt4PDH9DHhsU= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=/e6/6EUpmy8KU5oHHLsX64Tyd5jqOt575prpOrtJP D4=; b=VemePn5z+5i5/0SB0X7MrD0Y4s8yA06MJ3rAL3UzHUJ9FUUtf6SbBzMCa 1qu6Xu/4/xJuymY2aQxGch0nv4Ouswnf9teVjRZhgnG4GSe4FjaN4AuZG6B/VOjo lF4jvBBTVCPiVQq6ILEyHQM6R3zKFKhugKK5UNCWk0Y3SMAHLk8kzl4h4FzPJtfS 0Z2Hi8mX+OYY8En8sLiEIHygoIXHkMiP+fEsnxbJCdIyiTr8QOqNwD3770tmRxAq thQn99ZgJKJApCSLWtdoto9EkANi9/VqI3sbJQn8ftUPseXuE+yGBoXhnXvtFPSN wyazRQaRPqND1AvjglKt87Zhc2+Mg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrgeekgdekgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfh gggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceo thhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfe drudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvthenucevlhhushhtvghrufhiiigvpedu X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 0387FE469F; Thu, 17 Jan 2019 11:34:02 -0500 (EST) From: Thomas Monjalon To: David Marchand Cc: dev@dpdk.org, bruce.richardson@intel.com, solal.pirelli@gmail.com Date: Thu, 17 Jan 2019 17:34:01 +0100 Message-ID: <3463567.oezzxnnWpT@xps> In-Reply-To: <1547730777-20405-1-git-send-email-david.marchand@redhat.com> References: <1547730777-20405-1-git-send-email-david.marchand@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] eal: fix out of bound access when no cpu is available X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2019 16:34:06 -0000 17/01/2019 14:12, David Marchand: > In the unlikely case when the dpdk application is started with no cpu > available in the [0, RTE_MAX_LCORE - 1] range, the master_lcore is > automatically chosen as RTE_MAX_LCORE which triggers an out of bound > access. > > Either you have a crash then, or the initialisation fails later when > trying to pin the master thread on it. > In my test, with RTE_MAX_LCORE == 2: > > $ taskset -c 2 ./master/app/testpmd --no-huge -m 512 --log-level *:debug > [...] > EAL: pthread_setaffinity_np failed > PANIC in eal_thread_init_master(): > cannot set affinity > 7: [./master/app/testpmd() [0x47f629]] > > Bugzilla ID: 19 > Signed-off-by: David Marchand We should backport this fix. When this bug has been introduced?