netfilter-devel.vger.kernel.org archive mirror
 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: Thu, 30 Jul 2015 18:07:44 +0200	[thread overview]
Message-ID: <20150730160744.GA15008@salvia> (raw)
In-Reply-To: <2f95183cf2520b93d8443be935372fbef3499b96.1437561897.git.daniel@iogearbox.net>

On Wed, Jul 22, 2015 at 12:54:46PM +0200, Daniel Borkmann wrote:
> This patch replaces the zone id which is pushed down into functions
> with the actual zone object. It's a bigger one-time change, but
> needed for later on extending zones with a direction parameter, and
> thus decoupling this additional information from all call-sites.
> 
> No functional changes in this patch.
> 
> The default zones becomes a global const object, namely nf_ct_zone_dflt
> and will be returned directly in various cases, one being, when there's
> f.e. no zoning support.

Looks fine. This patchset depends on the recent fixes though, so let
me send a pull request to David with pending nf-next updates, then you
can rebase upon a fresh HEAD.

Regarding follow up patches, it would be good if you rename CTA_DIR to
CTA_ZONE_DIR. If you plan to place more information into the zone
extension, then it's probably a good idea to add a new nested
CTA_ZONE_INFO attribute where we can start adding new more information
on the zone configuration there that applies to the tuple.

I have seen also that you placed zone-dir= after use= in the sysctl
output, but you can place this after the zone instead. We have a
netlink interface so people should not be doing string parsing.

I'll make a closer look later to see if I have more comments. Thanks
for your patience, Daniel.

  reply	other threads:[~2015-07-30 16:01 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 [this message]
2015-07-30 16:34     ` Daniel Borkmann
2015-08-03 15:59       ` Pablo Neira Ayuso
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=20150730160744.GA15008@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 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).