From: Nick Bowler <nbowler@elliptictech.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: Regression, bisected: WARNING spam with ipsec since 2.6.35
Date: Fri, 17 Sep 2010 10:19:20 -0400 [thread overview]
Message-ID: <20100917141920.GA9280@elliptictech.com> (raw)
In-Reply-To: <1284676070.4784.25.camel@edumazet-laptop>
On 2010-09-17 00:27 +0200, Eric Dumazet wrote:
> I suspect following patch is needed, before further changes.
>
> [PATCH] xfrm: dont assume rcu_read_lock in xfrm_output_one()
Yup, that makes the warnings go away. Thanks.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2010-09-17 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100916213138.GA6605@elliptictech.com>
2010-09-16 22:27 ` Regression, bisected: WARNING spam with ipsec since 2.6.35 Eric Dumazet
2010-09-17 4:46 ` David Miller
2010-09-17 14:19 ` Nick Bowler [this message]
2010-09-17 15:03 ` Eric Dumazet
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=20100917141920.GA9280@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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).