From: Patrick McHardy <kaber@trash.net>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, Patrick McHardy <kaber@trash.net>,
netfilter-devel@vger.kernel.org
Subject: netfilter 00/06: netfilter fixes
Date: Tue, 24 Feb 2009 15:52:44 +0100 (MET) [thread overview]
Message-ID: <20090224145243.9789.60678.sendpatchset@x2.localnet> (raw)
Hi Dave,
the following patches contain netfilter fixes for 2.6.29:
- a typo fix in a ICMPv6 conntrack log message from Eric Leblond
- a fix for nfnetlink_log per-rule threshold overrides. Currently the
rule always wins because of the defaults, which is not intended.
Also from Eric.
- a fix for the nfnetlink_log default timeout units from Eric. The
kernel uses 10ms units, the default is specified in HZ.
- a fix to avoid conntrack event delivery for untracked connections
- a regression fix from Jan for a problem introduced in 2.6.28: the
/proc/net/ip_tables_matches and similar files don't include any
module registered with NFPROTO_UNSPEC. Unfortunately quite large.
- another regression fix from the kernel.org bugzilla: proc file
addition and removal of IPv4 addresses in recent match have ben
broken since the addition of IPv6 support.
The patches are also available in my nf-2.6.git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/kaber/nf-2.6.git
I've created it according to your suggestions, I hope everything is fine.
A small warning though: since its based on Linus' tree, it contains a lot
of commits not in net-2.6.git yet.
Please apply or pull, thanks.
include/linux/netfilter/xt_NFLOG.h | 2 +-
include/net/netfilter/nf_conntrack_core.h | 2 +-
net/ipv6/netfilter/nf_conntrack_proto_icmpv6.c | 5 +-
net/netfilter/nfnetlink_log.c | 8 +-
net/netfilter/x_tables.c | 199 +++++++++++++++++-------
net/netfilter/xt_recent.c | 2 +-
6 files changed, 153 insertions(+), 65 deletions(-)
Eric Leblond (3):
netfilter: nf_conntrack_ipv6: fix nf_log_packet message in icmpv6 conntrack
netfilter: nfnetlink_log: fix per-rule qthreshold override
netfilter: nfnetlink_log: fix timeout handling
Jan Engelhardt (1):
netfilter: make proc/net/ip* print names from foreign NFPROTO
Josef Drexler (1):
netfilter: xt_recent: fix proc-file addition/removal of IPv4 addresses
Patrick McHardy (1):
netfilter: nf_conntrack: don't try to deliver events for untracked connections
next reply other threads:[~2009-02-24 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 14:52 Patrick McHardy [this message]
2009-02-24 14:52 ` netfilter 01/06: nf_conntrack_ipv6: fix nf_log_packet message in icmpv6 conntrack Patrick McHardy
2009-02-24 14:52 ` netfilter 02/06: nfnetlink_log: fix per-rule qthreshold override Patrick McHardy
2009-02-24 14:52 ` netfilter 03/06: nfnetlink_log: fix timeout handling Patrick McHardy
2009-02-24 14:52 ` netfilter 04/06: nf_conntrack: don't try to deliver events for untracked connections Patrick McHardy
2009-02-24 14:52 ` netfilter 05/06: make proc/net/ip* print names from foreign NFPROTO Patrick McHardy
2009-02-24 14:52 ` netfilter 06/06: xt_recent: fix proc-file addition/removal of IPv4 addresses Patrick McHardy
2009-02-24 21:50 ` netfilter 00/06: netfilter fixes David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-08-18 16:51 Patrick McHardy
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=20090224145243.9789.60678.sendpatchset@x2.localnet \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.