From: David Miller <davem@davemloft.net>
To: jslaby@suse.cz
Cc: netdev@vger.kernel.org, jirislaby@gmail.com,
linux-kernel@vger.kernel.org, Priyanka.Jain@freescale.com
Subject: Re: [PATCH] NET: xfrm, use correct rcu dereference helper
Date: Sat, 18 Aug 2012 14:08:06 -0700 (PDT) [thread overview]
Message-ID: <20120818.140806.1408326124840020051.davem@davemloft.net> (raw)
In-Reply-To: <1345210716-24556-1-git-send-email-jslaby@suse.cz>
From: Jiri Slaby <jslaby@suse.cz>
Date: Fri, 17 Aug 2012 15:38:36 +0200
> Use rcu_dereference_bh while holding bh rcu lock. Otherwise we get:
> ===============================
> [ INFO: suspicious RCU usage. ]
> 3.6.0-rc1-next-20120816+ #10 Not tainted
> -------------------------------
> net/xfrm/xfrm_policy.c:2504 suspicious rcu_dereference_check() usage!
>
> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> Cc: Priyanka Jain <Priyanka.Jain@freescale.com>
Should already be fixed in net-next for at least a whole day now.
prev parent reply other threads:[~2012-08-18 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 13:38 [PATCH] NET: xfrm, use correct rcu dereference helper Jiri Slaby
2012-08-18 21:08 ` David Miller [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=20120818.140806.1408326124840020051.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Priyanka.Jain@freescale.com \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--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).