From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id C64BD9A8E for ; Fri, 27 Mar 2015 12:20:04 +0100 (CET) Received: by wgdm6 with SMTP id m6so95817585wgd.2 for ; Fri, 27 Mar 2015 04:20:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=SJeUegwfNmwqG06wT8FnEVqOGWd8UF2oFNlZIix5K4g=; b=dBhWxli+NTQD3OFqk4QP13wQZwIiIlBS8pfS2nl0VBMMlpeM9FyU2o2H6OGjWSrFVA 2ji2TReL1yDLz3T2krhr9JxDiyCWF0rbfHZ3Jkz1OjqSqDH74tW55B1m4fC+9i/EWbUC HyXYqYMaXfy1+6s01wX6aBksu0SaJ4CwfPIPbhZQT6ovB7w6sOJrtFAyQqQ16WCP9X3k 1xt217vHk2/t5CqaaoOi37kcgM9vPlZW6q9CATrTzZJRKfR9zQc5r7U9hkXwodBukSLi gZvVVMvvZYtNJ2ARhW3BnbJtWNMaqHmFsIUbP2kb0hzX4SXUQTlKOqAd+7S1IDlGDzaI FZYg== X-Gm-Message-State: ALoCoQl7NlBhsXU1B4iLL9kGQ6td2Anw6ZbNXlO5m7MrvmbCAIFIc+Y3n93hqbfJbEdSB0CzscEE X-Received: by 10.180.95.135 with SMTP id dk7mr21075276wib.64.1427455204725; Fri, 27 Mar 2015 04:20:04 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id jy7sm2972926wid.22.2015.03.27.04.20.03 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Mar 2015 04:20:03 -0700 (PDT) From: Thomas Monjalon To: "Gajdzica, MaciejX T" Date: Fri, 27 Mar 2015 12:19:23 +0100 Message-ID: <4339507.aQGAfvnUUj@xps13> Organization: 6WIND User-Agent: KMail/4.14.4 (Linux/3.18.4-1-ARCH; KDE/4.14.4; x86_64; ; ) In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D89126323382BD@IRSMSX108.ger.corp.intel.com> References: <1427123347-16200-1-git-send-email-maciejx.t.gajdzica@intel.com> <3EB4FA525960D640B5BDFFD6A3D89126323382BD@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] table: fix a crash during key8 and key32 overload X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2015 11:20:05 -0000 > > hash_key8_ext and hash_key32_ext tables allocate cache entries to > > support table overload cases. The crash can occur when cache entry is > > free after use. The problem is with computing the index of the free > > cache entry. The same case for key16 was fixed with earlier patch. > > > > Signed-off-by: Maciej Gajdzica > > Acked by: Cristian Dumitrescu Merged with Mirek's (key16) patch, thanks