netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: pablo@netfilter.org
To: netfilter-devel@vger.kernel.org
Subject: [PATCH 0/6] [RFC] ctnetlink updates for net-next
Date: Thu,  9 Feb 2012 20:33:01 +0100	[thread overview]
Message-ID: <1328815987-28020-1-git-send-email-pablo@netfilter.org> (raw)

From: Pablo Neira Ayuso <pablo@netfilter.org>

Hi,

The following are six patches for ctnetlink, four of them to finish
the expectation support (this is required by conntrackd, next version
will support expectation synchronization).

Two of them allows you to filter dumpings by mark. So we save cycles
on building and parsing messages. One for netlink itself, to allow
passing the filtering data (or whatever any other data you want to
pass to the ->dump and ->done callbacks).

Let me know if you have any comment. I'll push the to my tree if
nobody complains in the following days.

Thank you!

Pablo Neira Ayuso (6):
  netfilter: ctnetlink: allow to set helper for new expectations
  netfilter: ctnetlink: allow to set expectation class
  netfilter: ctnetlink: add NAT support for expectations
  netfilter: ctnetlink: allow to set expectfn for expectations
  netlink: netlink_dump_start may take data pointer for callbacks
  netfilter: ctnetlink: support kernel-space dump filterings

 crypto/crypto_user.c                          |    2 +-
 drivers/infiniband/core/netlink.c             |    2 +-
 include/linux/netfilter/nfnetlink_conntrack.h |   12 ++
 include/linux/netlink.h                       |    2 +
 include/net/netfilter/nf_conntrack_helper.h   |   13 ++
 net/core/rtnetlink.c                          |    2 +-
 net/ipv4/inet_diag.c                          |    4 +-
 net/ipv4/netfilter/nf_nat_core.c              |    8 ++
 net/ipv4/netfilter/nf_nat_h323.c              |   14 +++
 net/ipv4/netfilter/nf_nat_sip.c               |    7 +
 net/netfilter/ipset/ip_set_core.c             |    2 +-
 net/netfilter/nf_conntrack_helper.c           |   54 +++++++++
 net/netfilter/nf_conntrack_netlink.c          |  157 +++++++++++++++++++++++-
 net/netfilter/nfnetlink_acct.c                |    2 +-
 net/netlink/af_netlink.c                      |    2 +
 net/netlink/genetlink.c                       |    2 +-
 net/unix/diag.c                               |    2 +-
 net/xfrm/xfrm_user.c                          |    2 +-
 18 files changed, 272 insertions(+), 17 deletions(-)

-- 
1.7.7.3


             reply	other threads:[~2012-02-09 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 19:33 pablo [this message]
2012-02-09 19:33 ` [PATCH 1/6] netfilter: ctnetlink: allow to set helper for new expectations pablo
2012-02-09 19:33 ` [PATCH 2/6] netfilter: ctnetlink: allow to set expectation class pablo
2012-02-09 19:33 ` [PATCH 3/6] netfilter: ctnetlink: add NAT support for expectations pablo
2012-02-09 19:33 ` [PATCH 4/6] netfilter: ctnetlink: allow to set expectfn " pablo
2012-02-09 19:33 ` [PATCH 5/6] netlink: netlink_dump_start may take data pointer for callbacks pablo
2012-02-09 19:33 ` [PATCH 6/6] netfilter: ctnetlink: support kernel-space dump filterings pablo
  -- strict thread matches above, loose matches on Subject: below --
2012-02-09 20:03 [PATCH 0/6] [RFC] ctnetlink updates for net-next Hans Schillstrom

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=1328815987-28020-1-git-send-email-pablo@netfilter.org \
    --to=pablo@netfilter.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).