From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH] add TCP protocol state event groups
Date: Tue, 19 Jun 2007 15:33:51 +0200 [thread overview]
Message-ID: <4677DB3F.8010901@trash.net> (raw)
In-Reply-To: <466D8EEB.9080601@netfilter.org>
Pablo Neira Ayuso wrote:
> [CTNETLINK] add TCP protocol state event groups
>
> This patch adds per-protocol state event groups, so one can only listen to a
> certain TCP state change such as ESTABLISHED. Although such per-state message
> filtering could be done in userspace, we save CPU cycles since the kernel does
> not need to build and delivery messages that will be later discarded in
> userspace. This patch is particularly useful for conntrackd.
I can see that this is useful, but one group per protocol state
sounds rather excessive, I would expect that we could group them
more logically, maybe "connection setup, teardown and updates"?
Which states is conntrackd particulary interested in?
I would also like to hear from Holger whether his conntrack daemon
could make use of a mechnism like this too and if the filtering
capabilities you propose will do.
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
>
> --- net-2.6.git.orig/net/netfilter/nf_conntrack_netlink.c 2007-06-11 02:31:08.000000000 +0200
> +++ net-2.6.git/net/netfilter/nf_conntrack_netlink.c 2007-06-11 02:38:00.000000000 +0200
> @@ -317,7 +331,8 @@ static int ctnetlink_conntrack_event(str
> struct sk_buff *skb;
> unsigned int type;
> sk_buff_data_t b;
> - unsigned int flags = 0, group;
> + unsigned int flags = 0, group, proto_group;
> + bool proto_group_has_listener = false;
>
> /* ignore our fake conntrack entry */
> if (ct == &nf_conntrack_untracked)
> @@ -336,7 +351,11 @@ static int ctnetlink_conntrack_event(str
> } else
> return NOTIFY_DONE;
>
> - if (!nfnetlink_has_listeners(group))
> + proto_group = proto_event_group(ct);
> + if (proto_group != NFNLGRP_NONE && nfnetlink_has_listeners(proto_group))
> + proto_group_has_listener = true;
> +
> + if (!proto_group_has_listener && !nfnetlink_has_listeners(group))
> return NOTIFY_DONE;
>
> skb = alloc_skb(NLMSG_GOODSIZE, GFP_ATOMIC);
> @@ -396,7 +415,11 @@ static int ctnetlink_conntrack_event(str
> }
>
> nlh->nlmsg_len = skb->tail - b;
> + if (proto_group_has_listener)
> + atomic_inc(&skb->users);
> nfnetlink_send(skb, 0, group, 0);
This will always send to the main group even if only the proto group
has listeners.
next prev parent reply other threads:[~2007-06-19 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 18:05 [PATCH] add TCP protocol state event groups Pablo Neira Ayuso
2007-06-19 13:33 ` Patrick McHardy [this message]
2007-06-19 14:13 ` Pablo Neira Ayuso
2007-06-19 14:44 ` Patrick McHardy
2007-06-20 17:17 ` Pablo Neira Ayuso
2007-06-20 17:40 ` Patrick McHardy
2007-06-21 15:47 ` Pablo Neira Ayuso
2007-06-21 16:04 ` Patrick McHardy
2007-06-21 19:11 ` states worth to replicate [was Re: [PATCH] add TCP protocol state event groups] Pablo Neira Ayuso
2007-06-22 12:49 ` Patrick McHardy
2007-07-02 9:40 ` [PATCH] add TCP protocol state event groups Holger Eitzenberger
2007-07-02 15:36 ` 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=4677DB3F.8010901@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.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 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.