From: Hans Schillstrom <hans.schillstrom@ericsson.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: "eric.dumazet@gmail.com" <eric.dumazet@gmail.com>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"hans@schillstrom.com" <hans@schillstrom.com>
Subject: Re: [PATCH 1/1] conntrack, suspicious RCU usage
Date: Tue, 6 Mar 2012 06:58:15 +0100 [thread overview]
Message-ID: <201203060658.16156.hans.schillstrom@ericsson.com> (raw)
In-Reply-To: <20120305223815.GA30456@1984>
On Monday 05 March 2012 23:38:15 Pablo Neira Ayuso wrote:
> On Mon, Mar 05, 2012 at 06:05:48PM +0100, Pablo Neira Ayuso wrote:
> > On Mon, Mar 05, 2012 at 01:24:29PM +0100, Hans Schillstrom wrote:
> > > From: Hans Schillstrom <hans@schillstrom.com>
> > >
> > > Hello Pablo
> > > I think you lost this patch from Eric, I updated the patch for the
> > > latest nf_conntrack_netlink.c
> > >
> > > Well, __nf_ct_l4proto_find() being out of line and the way we already
> > > use rcu_read_lock() in this code, it seems following patch is
> > > the most natural way to cope with these lockdep warnings.
> >
> > I'll take the previous patch to pass it to current -rc. Thanks Hans.
>
> I'll pass it to net-next, otherwise this will result in one conflict
> with one patch already in net-next if I pass it to net.
>
Thanks a lot
/Hans
next prev parent reply other threads:[~2012-03-06 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 12:24 [PATCH 1/1] conntrack, suspicious RCU usage Hans Schillstrom
2012-03-05 17:05 ` Pablo Neira Ayuso
2012-03-05 22:38 ` Pablo Neira Ayuso
2012-03-06 5:58 ` Hans Schillstrom [this message]
2012-03-06 6:01 ` 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=201203060658.16156.hans.schillstrom@ericsson.com \
--to=hans.schillstrom@ericsson.com \
--cc=eric.dumazet@gmail.com \
--cc=hans@schillstrom.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).