From: Herbert Xu <herbert@gondor.apana.org.au>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: "David S. Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Thomas Graf <tgraf@suug.ch>
Subject: Re: rhashtable: warnings caused by "rhashtable: Fix use-after-free in rhashtable_walk_stop"
Date: Tue, 24 Mar 2015 08:55:13 +1100 [thread overview]
Message-ID: <20150323215513.GA20128@gondor.apana.org.au> (raw)
In-Reply-To: <55105B2E.1070409@oracle.com>
On Mon, Mar 23, 2015 at 02:27:58PM -0400, Sasha Levin wrote:
> Hi all,
>
> Commit 963ecbd41a ("rhashtable: Fix use-after-free in rhashtable_walk_stop") is causing
> RCU warnings since the code now locks a mutex (which might sleep) within an RCU critical
> section within rhashtable_walk_stop().
OK I will add a spin lock to bucket_table for this.
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
next prev parent reply other threads:[~2015-03-23 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 18:27 Sasha Levin
2015-03-23 21:55 ` Herbert Xu [this message]
2015-03-23 22:53 ` Herbert Xu
2015-03-24 2:16 ` David Miller
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=20150323215513.GA20128@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--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
all inboxes | Powered by JetHome®