From: Thomas Graf <tgraf@suug.ch>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: linux-next - crashes in rhashtable_shrink
Date: Thu, 29 Jan 2015 15:00:47 +0000 [thread overview]
Message-ID: <20150129150047.GB12634@casper.infradead.org> (raw)
In-Reply-To: <5398.1422543462@turing-police.cc.vt.edu>
On 01/29/15 at 09:57am, Valdis Kletnieks wrote:
> For the past few kernels, I've seen occasional crashes in rhashtable_shrink.
> Looks like the last thing to touch that code was the patch series:
>
> Subject [PATCH 0/9 net-next v2] rhashtable: Per bucket locks & deferred table resizing
> Date Fri, 2 Jan 2015 23:00:13 +0100
Thanks for the report! Based on a similar report I've already tracked
this down to race condition. I'm in the final stages of submitting a
series of fixes for it.
prev parent reply other threads:[~2015-01-29 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 14:57 linux-next - crashes in rhashtable_shrink Valdis Kletnieks
2015-01-29 15:00 ` Thomas Graf [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=20150129150047.GB12634@casper.infradead.org \
--to=tgraf@suug.ch \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).