From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] hash: fix lock release on add Date: Sat, 08 Jul 2017 19:00:50 +0200 Message-ID: <3606313.yn4QAvqHeP@xps> References: <1495801830-36849-1-git-send-email-mike.stolarchuk@bigswitch.com> <20170707055425.9357-1-pablo.de.lara.guarch@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, stable@dpdk.org To: Pablo de Lara , mstolarchuk Return-path: In-Reply-To: <20170707055425.9357-1-pablo.de.lara.guarch@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" 07/07/2017 07:54, Pablo de Lara: > From: mstolarchuk > > When adding items to a hash table with multiple threads, > there is an spinlock used to prevent data corruption > (unless Transactional Memory is supported). > > If there is a failure, the spinlock should be released, > but there were cases where that was not happening. > > Fixes: be856325cba3 ("hash: add scalable multi-writer insertion with Intel TSX") > CC: stable@dpdk.org > > Signed-off-by: mstolarchuk > Acked-by: Pablo de Lara Applied, thanks