From: Patrick McHardy <kaber@trash.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH 1/2] expr: remove secmark from ct and meta expression
Date: Wed, 15 Jan 2014 11:16:24 +0000 [thread overview]
Message-ID: <1389784585-17603-2-git-send-email-kaber@trash.net> (raw)
In-Reply-To: <1389784585-17603-1-git-send-email-kaber@trash.net>
The secctx should be used instead of the secmark. Remove for now.
Signed-off-by: Patrick McHardy <kaber@trash.net>
---
src/ct.c | 3 ---
src/meta.c | 2 --
src/parser.y | 3 ---
src/scanner.l | 1 -
4 files changed, 9 deletions(-)
diff --git a/src/ct.c b/src/ct.c
index b8f7632..f893df9 100644
--- a/src/ct.c
+++ b/src/ct.c
@@ -104,9 +104,6 @@ static const struct ct_template ct_templates[] = {
[NFT_CT_MARK] = CT_TEMPLATE("mark", &mark_type,
BYTEORDER_HOST_ENDIAN,
4 * BITS_PER_BYTE),
- [NFT_CT_SECMARK] = CT_TEMPLATE("secmark", &integer_type,
- BYTEORDER_HOST_ENDIAN,
- 4 * BITS_PER_BYTE),
[NFT_CT_EXPIRATION] = CT_TEMPLATE("expiration", &time_type,
BYTEORDER_HOST_ENDIAN,
4 * BITS_PER_BYTE),
diff --git a/src/meta.c b/src/meta.c
index d7b024b..6d42525 100644
--- a/src/meta.c
+++ b/src/meta.c
@@ -331,8 +331,6 @@ static const struct meta_template meta_templates[] = {
1 , BYTEORDER_HOST_ENDIAN),
[NFT_META_RTCLASSID] = META_TEMPLATE("rtclassid", &realm_type,
4 * 8, BYTEORDER_HOST_ENDIAN),
- [NFT_META_SECMARK] = META_TEMPLATE("secmark", &integer_type,
- 4 * 8, BYTEORDER_HOST_ENDIAN),
};
static void meta_expr_print(const struct expr *expr)
diff --git a/src/parser.y b/src/parser.y
index 7c18875..2e5f6c1 100644
--- a/src/parser.y
+++ b/src/parser.y
@@ -294,7 +294,6 @@ static void location_update(struct location *loc, struct location *rhs, int n)
%token SKGID "skgid"
%token NFTRACE "nftrace"
%token RTCLASSID "rtclassid"
-%token SECMARK "secmark"
%token CT "ct"
%token DIRECTION "direction"
@@ -1393,7 +1392,6 @@ meta_key : LENGTH { $$ = NFT_META_LEN; }
| SKGID { $$ = NFT_META_SKGID; }
| NFTRACE { $$ = NFT_META_NFTRACE; }
| RTCLASSID { $$ = NFT_META_RTCLASSID; }
- | SECMARK { $$ = NFT_META_SECMARK; }
;
meta_stmt : META meta_key SET expr
@@ -1412,7 +1410,6 @@ ct_key : STATE { $$ = NFT_CT_STATE; }
| DIRECTION { $$ = NFT_CT_DIRECTION; }
| STATUS { $$ = NFT_CT_STATUS; }
| MARK { $$ = NFT_CT_MARK; }
- | SECMARK { $$ = NFT_CT_SECMARK; }
| EXPIRATION { $$ = NFT_CT_EXPIRATION; }
| HELPER { $$ = NFT_CT_HELPER; }
| L3PROTOCOL { $$ = NFT_CT_L3PROTOCOL; }
diff --git a/src/scanner.l b/src/scanner.l
index 0b8abac..e813140 100644
--- a/src/scanner.l
+++ b/src/scanner.l
@@ -384,7 +384,6 @@ addrstring ({macaddr}|{ip4addr}|{ip6addr})
"skgid" { return SKGID; }
"nftrace" { return NFTRACE; }
"rtclassid" { return RTCLASSID; }
-"secmark" { return SECMARK; }
"ct" { return CT; }
"direction" { return DIRECTION; }
--
1.8.4.2
next prev parent reply other threads:[~2014-01-15 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 11:16 [PATCH 0/2] nftables: removal of secmark and shortened meta expressions Patrick McHardy
2014-01-15 11:16 ` Patrick McHardy [this message]
2014-01-15 11:16 ` [PATCH 2/2] meta: don't require "meta" keyword for a subset of " 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=1389784585-17603-2-git-send-email-kaber@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.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 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).