From: kaber@trash.net
To: davem@davemloft.net
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH 0/8] netfilter: netfilter update for net-next
Date: Thu, 21 Jul 2011 12:17:48 +0200 [thread overview]
Message-ID: <1311243476-18236-1-git-send-email-kaber@trash.net> (raw)
Hi Dave,
following is a netfilter update for net-next, containing:
- changes to the AUDIT target to log the security context, from Mr Dash Four
- RCUification of nfnetlink and nfnetlink_queue from Eric, raising performance
fourfold in his tests
- a fix for nfnetlink_queue to make sure packet IDs are monotonic increasing,
from Eric
- nfnetlink_queue batch verdict support from Florian, increasing performance
even further
- ipset updates from Jozsef
Please apply or pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/kaber/nf-next-2.6.git master
Thanks!
next reply other threads:[~2011-07-21 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 10:17 kaber [this message]
2011-07-21 10:17 ` [PATCH 1/8] netfilter: add SELinux context support to AUDIT target kaber
2011-07-21 10:17 ` [PATCH 2/8] netfilter: nfnetlink: add RCU in nfnetlink_rcv_msg() kaber
2011-07-21 10:17 ` [PATCH 3/8] netfilter: nfnetlink_queue: provide rcu enabled callbacks kaber
2011-07-21 10:17 ` [PATCH 4/8] netfilter: nfnetlink_queue: assert monotonic packet ids kaber
2011-07-21 10:17 ` [PATCH 5/8] netfilter: nfnetlink_queue: batch verdict support kaber
2011-07-21 10:17 ` [PATCH 6/8] netfilter: ipset: make possible to hash some part of the data element only kaber
2011-07-21 10:17 ` [PATCH 7/8] netfilter: ipset: hash:net,iface fixed to handle overlapping nets behind different interfaces kaber
2011-07-21 10:17 ` [PATCH 8/8] netfilter: ipset: fix compiler warnings "'hash_ip4_data_next' declared inline after being called" kaber
2011-07-21 19:50 ` [PATCH 0/8] netfilter: netfilter update for net-next David Miller
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=1311243476-18236-1-git-send-email-kaber@trash.net \
--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 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).