netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
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: rhashtable: warnings caused by "rhashtable: Fix use-after-free in rhashtable_walk_stop"
Date: Mon, 23 Mar 2015 14:27:58 -0400	[thread overview]
Message-ID: <55105B2E.1070409@oracle.com> (raw)

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().


Thanks,
Sasha

             reply	other threads:[~2015-03-23 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 18:27 Sasha Levin [this message]
2015-03-23 21:55 ` rhashtable: warnings caused by "rhashtable: Fix use-after-free in rhashtable_walk_stop" Herbert Xu
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=55105B2E.1070409@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).