From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Holger Eitzenberger <holger@eitzenberger.org>
Cc: netfilter-devel@vger.kernel.org, Krzysztof Piotr Oledzki <ole@ans.pl>
Subject: Re: [PATCH RFC 3/3] acct: add input and output interface index
Date: Thu, 17 Oct 2013 13:06:30 +0200 [thread overview]
Message-ID: <20131017110630.GA11148@localhost> (raw)
In-Reply-To: <20130926154005.592908761@eitzenberger.org>
Hi Holger,
I like patches 1/3 and 2/3, they are nice cleanups.
Some comments regarding this patch.
On Thu, Sep 26, 2013 at 05:31:53PM +0200, Holger Eitzenberger wrote:
> The interface indices are exported as uint32_t, although being
> signed integer inside the kernel, which goes in line with
> what nfnetlink_queue does.
>
> Both interface indices are wrapped inside CTA_ACCT.
>
> Signed-off-by: Holger Eitzenberger <holger@eitzenberger.org>
>
> Index: net-next-ipfix/include/net/netfilter/nf_conntrack_acct.h
> ===================================================================
> --- net-next-ipfix.orig/include/net/netfilter/nf_conntrack_acct.h
> +++ net-next-ipfix/include/net/netfilter/nf_conntrack_acct.h
> @@ -21,6 +21,8 @@ struct nf_conn_counter {
>
> struct nf_conn_acct {
> struct nf_conn_counter counter[IP_CT_DIR_MAX];
> + int indev;
> + int outdev;
> };
>
> static inline
> Index: net-next-ipfix/net/netfilter/nf_conntrack_core.c
> ===================================================================
> --- net-next-ipfix.orig/net/netfilter/nf_conntrack_core.c
> +++ net-next-ipfix/net/netfilter/nf_conntrack_core.c
> @@ -33,6 +33,7 @@
> #include <linux/mm.h>
> #include <linux/nsproxy.h>
> #include <linux/rculist_nulls.h>
> +#include <net/dst.h>
>
> #include <net/netfilter/nf_conntrack.h>
> #include <net/netfilter/nf_conntrack_l3proto.h>
> @@ -1110,6 +1111,7 @@ void __nf_ct_refresh_acct(struct nf_conn
> acct:
> if (do_acct) {
> struct nf_conn_acct *acct;
> + struct dst_entry *dst;
>
> acct = nf_conn_acct_find(ct);
> if (acct) {
> @@ -1117,6 +1119,13 @@ acct:
>
> atomic64_inc(&counter[CTINFO2DIR(ctinfo)].packets);
> atomic64_add(skb->len, &counter[CTINFO2DIR(ctinfo)].bytes);
> +
> + if (acct->indev == 0 && skb->dev)
> + acct->indev = skb->dev->ifindex;
> +
> + dst = skb_dst(skb);
> + if (acct->outdev == 0 && dst && dst->dev)
> + acct->outdev = dst->dev->ifindex;
If you only set indev/outdev once we can skip the conntrack extension
by passing the skb to nf_ct_deliver_cached_events and include this
information in the conntrack events. That would not allow to dump the
device from conntrack dumps though. I still have concerns with this
approach as this doesn't seem to cover the scenario in which the
in/outdev changes.
Regards.
next prev parent reply other threads:[~2013-10-17 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 15:31 [PATCH RFC 0/3] conntrack: add interface information to accounting extend Holger Eitzenberger
2013-09-26 15:31 ` [PATCH RFC 1/3] acct: introduce nf_conn_acct Holger Eitzenberger
2013-09-26 15:31 ` [PATCH RFC 2/3] ctnetlink: account both directions in one step Holger Eitzenberger
2013-09-26 15:31 ` [PATCH RFC 3/3] acct: add input and output interface index Holger Eitzenberger
2013-10-17 11:06 ` Pablo Neira Ayuso [this message]
2013-10-17 11:33 ` Holger Eitzenberger
2013-11-03 20:59 ` Pablo Neira Ayuso
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=20131017110630.GA11148@localhost \
--to=pablo@netfilter.org \
--cc=holger@eitzenberger.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=ole@ans.pl \
/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).