From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 52A824CC7; Sun, 18 Nov 2018 15:46:44 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D2C2521E0D; Sun, 18 Nov 2018 09:46:43 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 18 Nov 2018 09:46:43 -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=VD3iTwpCXQNFtCwjdOKbX22ap7pRFQNo98dTcojMefQ=; b=KEscY4dj1tZJ gmJcl8y8LoT4ErW0oL2DrYsdVYhNeZ/AUHDTBH6mt9eLmsf7voGZqkeQ78wiK7RU k0EHpSS+xR790gCWLu925OtM4PYO+7dzebxQpLUan/qO+xU5gxsI6X/gAzXiln+U yHFS8UWu+ek+fAFE6nbYxE5E8UHfQ8I= 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=VD3iTwpCXQNFtCwjdOKbX22ap7pRFQNo98dTcojMe fQ=; b=xNkuQblcbgRwVHm2QfNDlnHkqdvCBnXE4RYlSFf1NzbWtP7ZSO/JM7W8Z aJH1NrzOhAfxfHa+wSPD/n8GHqMNce2/3fOBENSoMe5gajfZMyDHI8V//mamhatY W1+FtzwxHEGcyij6b/wkJ30d6zLDsHLXLFs+Jh+46H+2KtHwLXgvC35iWQaTFOD2 pC2yzog5h4K95EBBRMEd4lLfBtTfJ6doY7TdqpCMsOt6q3d0ko7f/5uWGNuYKb0v O4BFWi+OjnujgNElB+mEW7De3kxOv5FgBALGVoLGwC7aPQHKe4hHOHuIs36Ex3ab /dA6XwrP5K7DKged5kDnIKkA+lAbg== X-ME-Sender: 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 8C085102F0; Sun, 18 Nov 2018 09:46:42 -0500 (EST) From: Thomas Monjalon To: Chaitanya Babu Talluri Cc: dev@dpdk.org, Ferruh Yigit , byron.marohn@intel.com, reshma.pattan@intel.com, pablo.de.lara.guarch@intel.com, stable@dpdk.org Date: Sun, 18 Nov 2018 15:46:41 +0100 Message-ID: <4704340.YbIWhMTtsl@xps> In-Reply-To: References: <1542113714-22607-1-git-send-email-tallurix.chaitanya.babu@intel.com> <1542194646-32724-1-git-send-email-tallurix.chaitanya.babu@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] lib/efd: fix write unlock during ring creation 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: Sun, 18 Nov 2018 14:46:44 -0000 16/11/2018 14:39, Ferruh Yigit: > On 11/14/2018 11:24 AM, Chaitanya Babu Talluri wrote: > > In rte_efd_create() write lock has already been unlocked > > before ring creation itself. > > So second unlock after the ring creation has been removed. > > > > Fixes: 56b6ef874f80 ("efd: new Elastic Flow Distributor library") > > Cc: stable@dpdk.org > > > > Signed-off-by: Chaitanya Babu Talluri > > Acked-by: Reshma Pattan > > Reviewed-by: Ferruh Yigit Applied, thanks