From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, denys@visp.net.lb
Subject: Re: [PATCH] netfilter: nf_conntrack_proto_gre: only create ct assured event once
Date: Mon, 3 Oct 2011 12:47:57 +0200 [thread overview]
Message-ID: <20111003104757.GA16052@1984> (raw)
In-Reply-To: <1317393509-11078-1-git-send-email-fw@strlen.de>
On Fri, Sep 30, 2011 at 04:38:29PM +0200, Florian Westphal wrote:
> GRE connections cause ctnetlink event flood due to ASSURED event
> being created for every packet received.
>
> Reported-and-tested-by: Denys Fedoryshchenko <denys@visp.net.lb>
> Signed-off-by: Florian Westphal <fw@strlen.de>
http://1984.lsi.us.es/git/?p=net/.git;a=shortlog;h=refs/heads/nf
Applied to my nf branch, thanks.
prev parent reply other threads:[~2011-10-03 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 14:38 [PATCH] netfilter: nf_conntrack_proto_gre: only create ct assured event once Florian Westphal
2011-10-03 10:47 ` Pablo Neira Ayuso [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=20111003104757.GA16052@1984 \
--to=pablo@netfilter.org \
--cc=denys@visp.net.lb \
--cc=fw@strlen.de \
--cc=netfilter-devel@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).