fixed chain name, chain rename and rule replacement
Subsystems (2)
v2 cover fixed chain name, chain rename and rule replacement
Hi,
Here a second version of the previous patchset, now taking care of chain's name issue. The name is fixed, same size as in iptables.
About an alternative, it could be possible to store a variable chain name in a separate allocated memory, kept in hash table: not the chain object itself, just the name. The key would be the chain's object pointer. At least, from execution point of view it would not affect anything since the name is necessary only for the user. The only issue is the memory occupied by such hash table.
I was looking quickly at the linux helpers, could not find a hashtable/map api, is there any? If so, I could try this idea of names stored like that.
Tomasz Bursztyka (4):
nf_tables: Change chain's name to be fixed sized
nf_tables: Add missing policy for NFTA_CHAIN_USE
nf_tables: Add support for changing users chain's name
nf_tables: Add support for replacing a rule by another one.
include/linux/netfilter/nf_tables.h | 3 ++ include/net/netfilter/nf_tables.h | 2 +- net/netfilter/nf_tables_api.c | 87 +++++++++++++++++++++++++++++++------ 3 files changed, 77 insertions(+), 15 deletions(-)
Signature · 1 line
1.7.12.4
PATCH v2 1/4 nf_tables: Change chain's name to be fixed sized
--- include/linux/netfilter/nf_tables.h | 2 ++ include/net/netfilter/nf_tables.h | 2 +- net/netfilter/nf_tables_api.c | 17 +++++++++-------- 3 files changed, 12 insertions(+), 9 deletions(-)
include/linux/netfilter/nf_tables.h +2 -0
@@ -1,6 +1,8 @@#ifndef _LINUX_NF_TABLES_H#define _LINUX_NF_TABLES_H +#define NFT_CHAIN_MAXNAMELEN 32 +enum nft_registers {NFT_REG_VERDICT , NFT_REG_1,
include/net/netfilter/nf_tables.h +1 -1
@@ -357,7 +357,7 @@ struct nft_chain {u16 use;u16 level;u16 hgenerator; -char name[]; +char name[NFT_CHAIN_MAXNAMELEN ]; };/**
net/netfilter/nf_tables_api.c +9 -8
@@ -478,7 +478,8 @@ static struct nft_chain *nf_tables_chain_lookup(const struct nft_table *table, }static const struct nla_policy nft_chain_policy[NFTA_CHAIN_MAX +1 ] = { - [NFTA_CHAIN_NAME ] = { .type =NLA_STRING }, + [NFTA_CHAIN_NAME ] = { .type =NLA_STRING , + .len =NFT_CHAIN_MAXNAMELEN -1 }, [NFTA_CHAIN_TABLE ] = { .type =NLA_STRING }, [NFTA_CHAIN_HOOK ] = { .type =NLA_NESTED }, [NFTA_CHAIN_POLICY ] = { .type =NLA_U32 },
@@ -687,7 +688,6 @@ static int nf_tables_newchain(struct sock *nlsk, struct sk_buff *skb,struct nft_chain *chain;struct nft_base_chain *basechain =NULL ;struct nlattr *ha[NFTA_HOOK_MAX +1 ]; -unsigned int size;int family = nfmsg->nfgen_family;int err;bool create;
@@ -723,7 +723,6 @@ static int nf_tables_newchain(struct sock *nlsk, struct sk_buff *skb,return 0 ; } - size =nla_len (name);if (nla[NFTA_CHAIN_HOOK ]) {struct nf_hook_ops *ops;
@@ -737,7 +736,7 @@ static int nf_tables_newchain(struct sock *nlsk, struct sk_buff *skb,if (ntohl (nla_get_be32 (ha[NFTA_HOOK_HOOKNUM ])) >= afi->nhooks)return -EINVAL ; - basechain =kzalloc (sizeof (*basechain) + size,GFP_KERNEL ); + basechain =kzalloc (sizeof (*basechain),GFP_KERNEL );if (basechain ==NULL )return -ENOMEM ; chain = &basechain->chain;
@@ -764,7 +763,7 @@ static int nf_tables_newchain(struct sock *nlsk, struct sk_buff *skb, } } }else { - chain =kzalloc (sizeof (*chain) + size,GFP_KERNEL ); + chain =kzalloc (sizeof (*chain),GFP_KERNEL );if (chain ==NULL )return -ENOMEM ;
@@ -772,7 +771,7 @@ static int nf_tables_newchain(struct sock *nlsk, struct sk_buff *skb, }INIT_LIST_HEAD (&chain->rules); -nla_strlcpy (chain->name, name, size); +nla_strlcpy (chain->name, name,NFT_CHAIN_MAXNAMELEN );list_add_tail (&chain->list, &table->chains);
@@ -1054,7 +1053,8 @@ static u16 nf_tables_rule_alloc_handle(struct nft_chain *chain)static const struct nla_policy nft_rule_policy[NFTA_RULE_MAX +1 ] = { [NFTA_RULE_TABLE ] = { .type =NLA_STRING }, - [NFTA_RULE_CHAIN ] = { .type =NLA_STRING }, + [NFTA_RULE_CHAIN ] = { .type =NLA_STRING , + .len =NFT_CHAIN_MAXNAMELEN -1 }, [NFTA_RULE_HANDLE ] = { .type =NLA_U16 }, [NFTA_RULE_EXPRESSIONS ] = { .type =NLA_NESTED }, };
@@ -2454,7 +2454,8 @@ EXPORT_SYMBOL_GPL(nft_validate_data_load);static const struct nla_policy nft_verdict_policy[NFTA_VERDICT_MAX +1 ] = { [NFTA_VERDICT_CODE ] = { .type =NLA_U32 }, - [NFTA_VERDICT_CHAIN ] = { .type =NLA_STRING }, + [NFTA_VERDICT_CHAIN ] = { .type =NLA_STRING , + .len =NFT_CHAIN_MAXNAMELEN -1 }, }; static int nft_verdict_init(const struct nft_ctx *ctx, struct nft_data *data,
Signature · 1 line
1.7.12.4
PATCH v2 2/4 nf_tables: Add missing policy for NFTA_CHAIN_USE
In reply to Tomasz Bursztyka--- net/netfilter/nf_tables_api.c | 1 + 1 file changed, 1 insertion(+)
net/netfilter/nf_tables_api.c +1 -0
@@ -483,6 +483,7 @@ static const struct nla_policy nft_chain_policy[NFTA_CHAIN_MAX + 1] = { [NFTA_CHAIN_TABLE] = { .type = NLA_STRING }, [NFTA_CHAIN_HOOK] = { .type = NLA_NESTED }, [NFTA_CHAIN_POLICY] = { .type = NLA_U32 }, + [NFTA_CHAIN_USE] = { .type = NLA_U32 }, };static const struct nla_policy nft_hook_policy[NFTA_HOOK_MAX +1 ] = {
Signature · 1 line
1.7.12.4
PATCH v2 3/4 nf_tables: Add support for changing users chain's name
In reply to Tomasz Bursztyka--- include/linux/netfilter/nf_tables.h | 1 + net/netfilter/nf_tables_api.c | 45 ++++++++++++++++++++++++++++++++++++- 2 files changed, 45 insertions(+), 1 deletion(-)
include/linux/netfilter/nf_tables.h +1 -0
@@ -69,6 +69,7 @@ enum nft_chain_attributes {NFTA_CHAIN_HOOK ,NFTA_CHAIN_POLICY ,NFTA_CHAIN_USE , +NFTA_CHAIN_NEW_NAME , __NFTA_CHAIN_MAX };#define NFTA_CHAIN_MAX (__NFTA_CHAIN_MAX - 1)
net/netfilter/nf_tables_api.c +44 -1
63 lines not on this page · raw message
Signature · 1 line
1.7.12.4
PATCH v2 4/4 nf_tables: Add support for replacing a rule by another one.
In reply to Tomasz Bursztyka--- net/netfilter/nf_tables_api.c | 24 +++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-)
net/netfilter/nf_tables_api.c +19 -5
@@ -1309,7 +1309,7 @@ static int nf_tables_newrule(struct sock *nlsk, struct sk_buff *skb,const struct nft_af_info *afi;const struct nft_table *table;struct nft_chain *chain; -struct nft_rule *rule; +struct nft_rule *rule, *old_rule =NULL ;struct nft_expr_info info[NFT_RULE_MAXEXPRS ];struct nft_expr *expr;struct nft_ctx ctx;
@@ -1345,9 +1345,11 @@ static int nf_tables_newrule(struct sock *nlsk, struct sk_buff *skb,if (rule !=NULL ) {if (nlh->nlmsg_flags &NLM_F_EXCL )return -EEXIST ; -if (nlh->nlmsg_flags &NLM_F_REPLACE ) -return -EOPNOTSUPP ; -return 0 ; +if (nlh->nlmsg_flags &NLM_F_REPLACE ) { + old_rule = rule; + rule =NULL ; + }else +return 0 ; } }else handle =nf_tables_rule_alloc_handle (chain);
@@ -1390,7 +1392,19 @@ static int nf_tables_newrule(struct sock *nlsk, struct sk_buff *skb, expr =nft_expr_next (expr); } -if (nlh->nlmsg_flags &NLM_F_APPEND ) +if (nlh->nlmsg_flags &NLM_F_REPLACE ) { +if (old_rule ==NULL ) + goto err2; + +list_replace_rcu (&old_rule->list, &rule->list); + +// FIXME: this makes deletion performance *really* suck +synchronize_rcu (); + +nf_tables_rule_notify (skb, nlh, table, chain, old_rule, +NFT_MSG_DELRULE , nfmsg->nfgen_family); +nf_tables_rule_destroy (&ctx, old_rule); + }else if (nlh->nlmsg_flags &NLM_F_APPEND )list_add_tail_rcu (&rule->list, &chain->rules);else list_add_rcu (&rule->list, &chain->rules);
Signature · 1 line
1.7.12.4
Pablo Neira Ayuso
maintainerHi Tomasz,
Quoted 11 lines · Tomasz Bursztyka
Hi,
Here a second version of the previous patchset, now taking care of chain's name issue. The name is fixed, same size as in iptables.
About an alternative, it could be possible to store a variable chain name in a separate allocated memory, kept in hash table: not the chain object itself, just the name. The key would be the chain's object pointer. At least, from execution point of view it would not affect anything since the name is necessary only for the user. The only issue is the memory occupied by such hash table.
We can declare a const char * inside nft_chain and kmalloc the area for the name dynamically. If renamed, we can reallocation it. It's simple, but we increase memory fragmentation.
Quoted 3 lines
I was looking quickly at the linux helpers, could not find a hashtable/map api, is there any? If so, I could try this idea of names stored like that.
There have been some discussion regarding generic hashtable API since long time.
http://www.spinics.net/lists/linux-nfs/msg33526.html
It seems Linus is going to take it.
Quoted 5 lines
Tomasz Bursztyka (4):
nf_tables: Change chain's name to be fixed sized
nf_tables: Add missing policy forNFTA_CHAIN_USE
nf_tables: Add support for changing users chain's name
nf_tables: Add support for replacing a rule by another one.
I've taken these three to nf_tables-experiments branch.
Thanks a lot.