From: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
To: netfilter-devel@vger.kernel.org
Cc: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Subject: [iptables-nftables - RFC PATCH 10/15] nft: Register all relevant xtables extensions into translation tree
Date: Fri, 19 Jul 2013 18:17:39 +0300 [thread overview]
Message-ID: <1374247064-3361-11-git-send-email-tomasz.bursztyka@linux.intel.com> (raw)
In-Reply-To: <1374247064-3361-1-git-send-email-tomasz.bursztyka@linux.intel.com>
Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
---
include/xtables.h.in | 3 +++
iptables/nft-xt-ext.c | 13 +++++++++++++
2 files changed, 16 insertions(+)
diff --git a/include/xtables.h.in b/include/xtables.h.in
index 592aae9..0f02470 100644
--- a/include/xtables.h.in
+++ b/include/xtables.h.in
@@ -403,6 +403,9 @@ extern "C" {
#endif
extern const char *xtables_modprobe_program;
+
+extern struct xtables_match *xtables_pending_matches;
+extern struct xtables_target *xtables_pending_targets;
extern struct xtables_match *xtables_matches;
extern struct xtables_target *xtables_targets;
diff --git a/iptables/nft-xt-ext.c b/iptables/nft-xt-ext.c
index ffc53f0..2ce8b70 100644
--- a/iptables/nft-xt-ext.c
+++ b/iptables/nft-xt-ext.c
@@ -138,12 +138,25 @@ static struct nft_trans_instruction nft_ipt_xt_match = {
int nft_xt_ext_into_translation_tree(struct nft_trans_instruction_tree *tree)
{
+ struct xtables_target *t;
+ struct xtables_match *m;
+
if (tree == NULL)
return -1;
nft_trans_add_instruction(tree, &nft_ipt_xt_target);
nft_trans_add_instruction(tree, &nft_ipt_xt_match);
+ for (t = xtables_pending_targets; t; t = t->next) {
+ if (t->register_nft_instructions != NULL)
+ t->register_nft_instructions(tree);
+ }
+
+ for (m = xtables_pending_matches; m; m = m->next) {
+ if (m->register_nft_instructions != NULL)
+ m->register_nft_instructions(tree);
+ }
+
return 0;
}
--
1.8.3.2
next prev parent reply other threads:[~2013-07-19 15:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 15:17 [iptables-nftables - RFC PATCH 00/15] Xtables extensions: full support (pure nft or compat layer) Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 01/15] xtables: Add support for injecting xtables target into nft rule Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 02/15] xtables: add support for injecting xtables matches " Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 03/15] nft: Add nft expressions translation engine as a library Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 04/15] nft: Integrate nft translator engine in current core Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 05/15] nft: Manage xtables target parsing through translation tree Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 06/15] nft: Manage xtables matches through nft " Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 07/15] nft: Add support for xtables extensions callback to change cs Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 08/15] xtables: Add support for registering nft translation function for target Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 09/15] xtables: Add support for registering nft translation function for match Tomasz Bursztyka
2013-07-19 15:17 ` Tomasz Bursztyka [this message]
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 11/15] nft: Refactor firewall printing so it reuses already parsed cs struct Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 12/15] nft: Refactor rule deletion so it compares both cs structure Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 13/15] nft: Remove useless function Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 14/15] xtables: nft: Complete refactoring on how rules are saved Tomasz Bursztyka
2013-07-19 15:17 ` [iptables-nftables - RFC PATCH 15/15] xtables: Support pure nft expressions for DNAT extension Tomasz Bursztyka
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=1374247064-3361-11-git-send-email-tomasz.bursztyka@linux.intel.com \
--to=tomasz.bursztyka@linux.intel.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 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).