All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: tgraf@suug.ch, challa@noironetworks.com, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next v3 1/3] netfilter: nf_conntrack: push zone object into functions
Date: Mon, 3 Aug 2015 17:59:09 +0200	[thread overview]
Message-ID: <20150803155909.GA17212@salvia> (raw)
In-Reply-To: <55BA5228.6050908@iogearbox.net>

On Thu, Jul 30, 2015 at 06:34:48PM +0200, Daniel Borkmann wrote:
> CTA_ZONE_DIR seems better, sure. I don't have any other extensions at
> the moment, but it seems it makes sense to make this nested at this
> point in time, so we have CTA_ZONE and CTA_ZONE_INFO as a container
> for CTA_ZONE_DIR and whatever future might bring. I will look into it.

thinking it well, this is part of the tuple, so I'd suggest you add
CTA_TUPLE_ZONE to enum ctattr_tuple. We will probably need later to
place each tuple in different zones.

  reply	other threads:[~2015-08-03 15:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 10:54 [PATCH nf-next v3 0/3] Netfilter zone directions Daniel Borkmann
2015-07-22 10:54 ` [PATCH nf-next v3 1/3] netfilter: nf_conntrack: push zone object into functions Daniel Borkmann
2015-07-30 16:07   ` Pablo Neira Ayuso
2015-07-30 16:34     ` Daniel Borkmann
2015-08-03 15:59       ` Pablo Neira Ayuso [this message]
2015-08-03 16:00         ` Daniel Borkmann
2015-08-05 10:51           ` Pablo Neira Ayuso
2015-08-05 14:00             ` Daniel Borkmann
2015-08-06 10:02               ` Pablo Neira Ayuso
2015-07-22 10:54 ` [PATCH nf-next v3 2/3] netfilter: nf_conntrack: add direction support for zones Daniel Borkmann
2015-07-22 10:54 ` [PATCH nf-next v3 3/3] netfilter: nf_conntrack: add efficient mark to zone mapping Daniel Borkmann

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=20150803155909.GA17212@salvia \
    --to=pablo@netfilter.org \
    --cc=challa@noironetworks.com \
    --cc=daniel@iogearbox.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /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.