From: Eric Dumazet <eric.dumazet@gmail.com>
To: Paul Moore <paul.moore@hp.com>
Cc: netdev@vger.kernel.org, "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH] netlabel: Fix several rcu_dereference() calls used without RCU read locks
Date: Thu, 01 Apr 2010 22:56:47 +0200 [thread overview]
Message-ID: <1270155407.2192.5.camel@edumazet-laptop> (raw)
In-Reply-To: <20100401204357.9795.80383.stgit@flek.lan>
Le jeudi 01 avril 2010 à 16:43 -0400, Paul Moore a écrit :
> The recent changes to add RCU lock verification to rcu_dereference() calls
> caught out a problem with netlbl_unlhsh_hash(), see below.
>
> ===================================================
> [ INFO: suspicious rcu_dereference_check() usage. ]
> ---------------------------------------------------
> net/netlabel/netlabel_unlabeled.c:246 invoked rcu_dereference_check()
> without protection!
>
> This patch fixes this problem as well as others like it in the NetLabel
> code. Also included in this patch is the identification of future work
> to eliminate the RCU read lock in netlbl_domhsh_add(), but in the interest
> of getting this patch out quickly that work will happen in another patch
> to be finished later.
>
> Thanks to Eric Dumazet and Paul McKenney for their help in understanding
> the recent RCU changes.
>
> Signed-off-by: Paul Moore <paul.moore@hp.com>
> Reported-by: David Howells <dhowells@redhat.com>
> CC: Eric Dumazet <eric.dumazet@gmail.com>
> CC: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> ---
> net/netlabel/netlabel_domainhash.c | 28 ++++++++++-----
> net/netlabel/netlabel_unlabeled.c | 66 ++++++++++--------------------------
> 2 files changed, 37 insertions(+), 57 deletions(-)
>
Acked-by: Eric Dumazet <eric.dumazet@gmail.com>
Thanks Paul
next prev parent reply other threads:[~2010-04-01 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 20:43 [PATCH] netlabel: Fix several rcu_dereference() calls used without RCU read locks Paul Moore
2010-04-01 20:56 ` Eric Dumazet [this message]
2010-04-02 0:27 ` 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=1270155407.2192.5.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=paulmck@linux.vnet.ibm.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