From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id C66EEA00E6 for ; Wed, 10 Jul 2019 23:26:59 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 95A22324D; Wed, 10 Jul 2019 23:26:58 +0200 (CEST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by dpdk.org (Postfix) with ESMTP id C64562C60; Wed, 10 Jul 2019 23:26:56 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 254DE43B; Wed, 10 Jul 2019 17:26:53 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 10 Jul 2019 17:26:53 -0400 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=8/XB3a3n82TA/5g5rvheEuczRtd06gIbj8SWPcmIVTs=; b=NA7yJPInnRF4 YTSGFkweVmKL2xd+oyFOUseeaiZp+bPhQMw9KJ66LxEg35kxA3LU+e140dGMfr7s GHd9ctGNOIOKw6h0SiAerh3gG8881+20JpkJYASqNa/WKSi+IRVZjaxmUVGZxptp JzcmoaPeZXAP1bcHyvQ9kgrVXPRred4= 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=fm3; bh=8/XB3a3n82TA/5g5rvheEuczRtd06gIbj8SWPcmIV Ts=; b=h3wIA52/cU/G2ndraxwPPeLQMy1Z2Xc2hXF2gAdOXio7dOo0XhQU2MbB6 0tFGd86lNfbI14ZDaC7ApELKZOTOqtm5CNKmYw8x1EjYzZhQJKNPRaMCqwbPW4J6 PDvyi6DMI21gxmXaf4orLhzU4njPATOYcciCZhvZGh0whiZAwNotgaNNwkjwHM5K n2v0rcMST19zvnV2aYuTJy+XX+VLywrKgvidfybhyU9c+iU+LoHoNNDh0rUFLv7A XrKrg7gPXLVrZzj5LnmrUdASRRkNEcgQM1Xf9We6MdHqxZ5ELtafGrbR37v1hQJo IjfGyqojirjlA+VmyQNuyIcElvMiQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrgeeigdduieegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt 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 7441680061; Wed, 10 Jul 2019 17:26:51 -0400 (EDT) From: Thomas Monjalon To: Anatoly Burakov Cc: dev@dpdk.org, patrick.fu@intel.com, stable@dpdk.org Date: Wed, 10 Jul 2019 23:26:50 +0200 Message-ID: <4178981.6ck5SrQ1kV@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] fbarray: fix fbarray destruction 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 09/07/2019 16:00, Anatoly Burakov: > Currently, when fbarray is destroyed, the fbarray structure is not > zeroed out, which leads to stale data being there and confusing > secondary process init in legacy mem mode. Fix it by always > memsetting the fbarray to zero when destroying it. > > Fixes: 5b61c62cfd76 ("fbarray: add internal tailq for mapped areas") > Cc: stable@dpdk.org > > Signed-off-by: Anatoly Burakov Applied, thanks