From: Thomas Graf <tgraf@suug.ch>
To: Ying Xue <ying.xue@windriver.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH 0/6 net-next] rhashtable fixes
Date: Tue, 3 Feb 2015 17:21:13 +0000 [thread overview]
Message-ID: <20150203172113.GC25410@casper.infradead.org> (raw)
In-Reply-To: <54CB5563.9080000@windriver.com>
On 01/30/15 at 05:56pm, Ying Xue wrote:
> On 01/30/2015 05:29 PM, Thomas Graf wrote:
> > Right, I see the same soft lockup. Interestingly I cannot trigger it
> > with the rht test code. I can only trigger it with your Netlink socket
> > creation stress test. It is definitely related to the deferred worker,
> > when I disable growing, then the bug disappears.
>
> Yes, when I disable expansion, the soft lockup also disappears too.
I have found the last remaining race and can now run your test
program successfully in an endless loop.
I will resubmit a v2 of this series.
next prev parent reply other threads:[~2015-02-03 17:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 0:20 [PATCH 0/6 net-next] rhashtable fixes Thomas Graf
2015-01-30 0:20 ` [PATCH 1/6] rhashtable: key_hashfn() must return full hash value Thomas Graf
2015-01-30 0:20 ` [PATCH 2/6] rhashtable: Use a single bucket lock for sibling buckets Thomas Graf
2015-01-31 4:34 ` Herbert Xu
2015-01-31 8:41 ` Thomas Graf
2015-01-31 9:38 ` Herbert Xu
2015-01-31 12:50 ` Thomas Graf
2015-01-30 0:20 ` [PATCH 3/6] rhashtable: Wait for RCU readers after final unzip work Thomas Graf
2015-01-30 0:20 ` [PATCH 4/6] rhashtable: Dump bucket tables on locking violation under PROVE_LOCKING Thomas Graf
2015-01-30 0:20 ` [PATCH 5/6] rhashtable: Add more lock verification Thomas Graf
2015-01-30 0:20 ` [PATCH 6/6] rhashtable: Avoid bucket cross reference after removal Thomas Graf
2015-01-30 9:10 ` [PATCH 0/6 net-next] rhashtable fixes Ying Xue
2015-01-30 9:29 ` Thomas Graf
2015-01-30 9:56 ` Ying Xue
2015-02-03 17:21 ` Thomas Graf [this message]
2015-02-04 2:32 ` Ying Xue
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=20150203172113.GC25410@casper.infradead.org \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ying.xue@windriver.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).