From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] fbarray: fix init unlock without lock Date: Fri, 29 Mar 2019 12:50:22 +0100 Message-ID: <33065672.VFaiPrc4eW@xps> References: <35fe9a105fbf7868fc34cef330745b33acd0527c.1553856703.git.anatoly.burakov@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, dariusz.stojaczyk@intel.com, gavin.hu@arm.com To: Anatoly Burakov Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 831155A for ; Fri, 29 Mar 2019 12:50:25 +0100 (CET) In-Reply-To: <35fe9a105fbf7868fc34cef330745b33acd0527c.1553856703.git.anatoly.burakov@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 29/03/2019 11:57, Anatoly Burakov: > Certain failure paths of rte_fbarray_init() will unlock the > mem area lock without locking it first. Fix this by properly > handling the failures. > > Fixes: 5b61c62cfd76 ("fbarray: add internal tailq for mapped areas") > > Signed-off-by: Anatoly Burakov Applied, thanks