DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	mstolarchuk <mike.stolarchuk@bigswitch.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] __rte_hash_add_key_with_hash not	releasing	multiwriter_lock in failure paths
Date: Fri, 7 Jul 2017 13:55:36 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBD8135@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CBD6770@IRSMSX108.ger.corp.intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch,
> Pablo
> Sent: Wednesday, July 5, 2017 3:51 PM
> To: mstolarchuk <mike.stolarchuk@bigswitch.com>; Richardson, Bruce
> <bruce.richardson@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] __rte_hash_add_key_with_hash not
> releasing multiwriter_lock in failure paths
> 
> 
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of mstolarchuk
> > Sent: Friday, May 26, 2017 1:31 PM
> > To: bruce.richardson@intel.co
> > Cc: dev@dpdk.org
> > Subject: [dpdk-dev] [PATCH] __rte_hash_add_key_with_hash not
> releasing
> > multiwriter_lock in failure paths
> >
> > Signed-off-by: mstolarchuk <mike.stolarchuk@bigswitch.com>
> > ---
> >  lib/librte_hash/rte_cuckoo_hash.c | 13 +++++++++----
> >  1 file changed, 9 insertions(+), 4 deletions(-)
> >
> > diff --git a/lib/librte_hash/rte_cuckoo_hash.c
> > b/lib/librte_hash/rte_cuckoo_hash.c
> > index 645c0cf..37a8110 100644
> > --- a/lib/librte_hash/rte_cuckoo_hash.c
> > +++ b/lib/librte_hash/rte_cuckoo_hash.c
> > @@ -538,8 +538,10 @@ struct rte_hash *
> >  			n_slots = rte_ring_mc_dequeue_burst(h-
> > >free_slots,
> >  					cached_free_slots->objs,
> >  					LCORE_CACHE_SIZE, NULL);
> > -			if (n_slots == 0)
> > -				return -ENOSPC;
> > +			if (n_slots == 0) {
> > +				ret = -ENOSPC;
> > +				goto failure;
> > +			}
> >
> >  			cached_free_slots->len += n_slots;
> >  		}
> > @@ -548,8 +550,10 @@ struct rte_hash *
> >  		cached_free_slots->len--;
> >  		slot_id = cached_free_slots->objs[cached_free_slots->len];
> >  	} else {
> > -		if (rte_ring_sc_dequeue(h->free_slots, &slot_id) != 0)
> > -			return -ENOSPC;
> > +		if (rte_ring_sc_dequeue(h->free_slots, &slot_id) != 0) {
> > +			ret = -ENOSPC;
> > +			goto failure;
> > +		}
> >  	}
> >
> >  	new_k = RTE_PTR_ADD(keys, (uintptr_t)slot_id * h-
> > >key_entry_size); @@ -659,6 +663,7 @@ struct rte_hash *
> >  	/* Error in addition, store new slot back in the ring and return
> > error */
> >  	enqueue_slot_back(h, cached_free_slots, (void *)((uintptr_t)
> > new_idx));
> >
> > +failure:
> >  	if (h->add_key == ADD_KEY_MULTIWRITER)
> >  		rte_spinlock_unlock(h->multiwriter_lock);
> >  	return ret;
> > --
> > 1.9.1
> 
> Hi  Mike,
> 
> Thanks for the patch, it looks correct to me.
> The code is fine, but the commit message needs some rework.
> Title should start with: "hash: ...", since this is aiming the hash library, So
> the title could be: "hash: fix lock release on add"
> 
> Then, some explanation on what the fix is doing would be good.
> 
> Lastly, since this is a fix, it requires a fixes line and CC to the stable branch:
> 
> Fixes: be856325cba3 ("hash: add scalable multi-writer insertion with Intel
> TSX")
> CC: stable@dpdk.org

FYI, I just submitted a v2 with the commit fixed for you, as you might not be available
these days and the RC1 will be created soon.

Pablo
> 
> Thanks,
> Pablo

  reply	other threads:[~2017-07-07 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 12:30 mstolarchuk
2017-07-05 14:50 ` De Lara Guarch, Pablo
2017-07-07 13:55   ` De Lara Guarch, Pablo [this message]
2017-07-07  5:54 ` [dpdk-dev] [PATCH v2] hash: fix lock release on add Pablo de Lara
2017-07-08 17:00   ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E115CCD9D858EF4F90C690B0DCB4D8976CBD8135@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mike.stolarchuk@bigswitch.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).