Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1162612AbbKTMZx (ORCPT ); Fri, 20 Nov 2015 07:25:53 -0500 Received: from helcar.hengli.com.au ([209.40.204.226]:33628 "EHLO helcar.hengli.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760013AbbKTMZw (ORCPT ); Fri, 20 Nov 2015 07:25:52 -0500 Date: Fri, 20 Nov 2015 20:25:44 +0800 From: Herbert Xu To: Phil Sutter , Xin Long , linux-kernel@vger.kernel.org, network dev , tgraf@suug.ch, davem Subject: Re: rhashtable: how to deal with that rhashtable_lookup_insert_key return -EBUSY Message-ID: <20151120122544.GA17528@gondor.apana.org.au> References: <20151120122401.GB16648@orbit.nwl.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151120122401.GB16648@orbit.nwl.cc> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 781 Lines: 19 On Fri, Nov 20, 2015 at 01:24:01PM +0100, Phil Sutter wrote: > > Herbert, did you manage to reproduce the problem meanwhile? If so, was > there any progress on fixing rhashtable? Otherwise, I could respin my > patch from [1] to cover only -EBUSY case by default and add a parameter > to make non-permanent -ENOMEM visible. No I have not been able to reproduce this yet. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/