From: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [RFC nftables kernel PATCH] netfilter: nf_tables: fix nft_meta_target module
Date: Thu, 28 Nov 2013 14:33:51 +0200 [thread overview]
Message-ID: <5297382F.60707@linux.intel.com> (raw)
In-Reply-To: <20131128111557.6154.40370.stgit@nfdev.cica.es>
Hi Arturo,
Minor stuff:
> + * @NFT_META_TARGET_MARK: to stablish packet mark (skb->mark)
to 'e'stablish
Why not reusing existing NFT_META_* keys?
It would just raise an error if not priority/mark/nftrace/secmark, as it
does currently.
Worth to keep that as it is imho, no need to duplicate.
Besides that, any other name that would be more relevant than meta_target?
Target is already a critical in-use keyword in netfilter, so it's not
clear enough.
All expression have a short, one-word based name, which is nice.
Anyway, doesn't it work already: if you create an immediate expression
(to load the value you want, at default dreg 0 aka NFT_REG_VERDICT) and
a meta expression without the NFTA_META_DREG set? (didn't try myself)
If not maybe there is a shorter way to fix this, instead of creating a
full new expression. Looks like it was the original plan.
Tomasz
next prev parent reply other threads:[~2013-11-28 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 11:15 [RFC nftables kernel PATCH] netfilter: nf_tables: fix nft_meta_target module Arturo Borrero Gonzalez
2013-11-28 12:33 ` Tomasz Bursztyka [this message]
2013-11-28 13:15 ` Arturo Borrero Gonzalez
2013-11-28 13:32 ` Tomasz Bursztyka
2013-11-28 14:33 ` Arturo Borrero Gonzalez
2013-11-29 5:52 ` Tomasz Bursztyka
2013-12-04 13:21 ` Pablo Neira Ayuso
2013-12-04 13:30 ` Tomasz Bursztyka
2013-12-04 15:05 ` Arturo Borrero Gonzalez
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=5297382F.60707@linux.intel.com \
--to=tomasz.bursztyka@linux.intel.com \
--cc=arturo.borrero.glez@gmail.com \
--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 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.