From: Herbert Xu <herbert@gondor.apana.org.au>
To: Phil Sutter <phil@nwl.cc>, Xin Long <lucien.xin@gmail.com>,
linux-kernel@vger.kernel.org,
network dev <netdev@vger.kernel.org>,
tgraf@suug.ch, davem <davem@davemloft.net>
Subject: Re: rhashtable: how to deal with that rhashtable_lookup_insert_key return -EBUSY
Date: Fri, 20 Nov 2015 20:25:44 +0800 [thread overview]
Message-ID: <20151120122544.GA17528@gondor.apana.org.au> (raw)
In-Reply-To: <20151120122401.GB16648@orbit.nwl.cc>
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 <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2015-11-20 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 5:14 rhashtable: how to deal with that rhashtable_lookup_insert_key return -EBUSY Xin Long
2015-11-20 12:24 ` Phil Sutter
2015-11-20 12:25 ` Herbert Xu [this message]
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=20151120122544.GA17528@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=tgraf@suug.ch \
/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