From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nf-next/nf_tables-experiments - PATCH 1/2] nf_tables: Add support for changing users chain's name
Date: Wed, 31 Oct 2012 14:49:24 +0100 [thread overview]
Message-ID: <20121031134924.GA1060@1984> (raw)
In-Reply-To: <1351675709-14127-2-git-send-email-tomasz.bursztyka@linux.intel.com>
Hi Tomasz,
The patchset looks good, I just have a comment on this one.
>From net/netfilter/nf_tables_core.c:
case NFT_GOTO:
chain = data[NFT_REG_VERDICT].chain;
In the GOTO case, we already point to the chain object. That chain
object is loaded in nft_immediate.c _eval(). However, the private data
of immediate is initialized in the _init() path. That means we would
need to refresh the entire rule-set to point to the correct new chain
object, otherwise we would crash.
I'd follow a simpler solution to avoid issues. Use a fixed chain name
length (the same length as iptables does, or just 32 bytes).
We can revisit this later to see if we can support renaming and
dynamically allocated chain objects at the same time.
Would you resend a new version of this patch?
Thanks.
On Wed, Oct 31, 2012 at 11:28:28AM +0200, Tomasz Bursztyka wrote:
> Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
> ---
> include/linux/netfilter/nf_tables.h | 1 +
> net/netfilter/nf_tables_api.c | 58 ++++++++++++++++++++++++++++++++++++-
> 2 files changed, 58 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/netfilter/nf_tables.h b/include/linux/netfilter/nf_tables.h
> index 0115a2f..542b654 100644
> --- a/include/linux/netfilter/nf_tables.h
> +++ b/include/linux/netfilter/nf_tables.h
> @@ -67,6 +67,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)
> diff --git a/net/netfilter/nf_tables_api.c b/net/netfilter/nf_tables_api.c
> index e0e4616..fd1b624 100644
> --- a/net/netfilter/nf_tables_api.c
> +++ b/net/netfilter/nf_tables_api.c
> @@ -676,6 +676,62 @@ nf_tables_chain_policy(struct nft_chain *chain, const struct nlattr *attr)
> return 0;
> }
>
> +static int nf_tables_mvchain(struct sk_buff *skb, const struct nlmsghdr *nlh,
> + struct nft_table *table,
> + struct nft_chain *old_chain,
> + const struct nlattr * const nla[])
> +{
> + const struct nfgenmsg *nfmsg = nlmsg_data(nlh);
> + int family = nfmsg->nfgen_family;
> + struct nft_chain *new_chain;
> + const struct nlattr *name;
> + unsigned int size;
> +
> + if (!nla[NFTA_CHAIN_NEW_NAME])
> + return -EINVAL;
> +
> + if (old_chain->flags & NFT_CHAIN_BUILTIN ||
> + old_chain->flags & NFT_BASE_CHAIN)
> + return -EOPNOTSUPP;
> +
> + if (old_chain->use > 0)
> + return -EBUSY;
> +
> + name = nla[NFTA_CHAIN_NEW_NAME];
> + new_chain = nf_tables_chain_lookup(table, name);
> + if (IS_ERR(new_chain)) {
> + if (PTR_ERR(new_chain) != -ENOENT)
> + return PTR_ERR(new_chain);
> + new_chain = NULL;
> + }
> +
> + if (new_chain != NULL)
> + return -EEXIST;
> +
> + size = nla_len(name);
> + new_chain = kzalloc(sizeof(*new_chain) + size, GFP_KERNEL);
> + if (new_chain == NULL)
> + return -ENOMEM;
> +
> + list_del(&old_chain->list);
> +
> + INIT_LIST_HEAD(&new_chain->rules);
> + nla_strlcpy(new_chain->name, name, size);
> +
> + /* Copying content from old chain */
> + new_chain->flags = old_chain->flags;
> + list_replace_init(&old_chain->rules, &new_chain->rules);
> +
> + list_add_tail(&new_chain->list, &table->chains);
> +
> + nf_tables_chain_notify(skb, nlh, table, old_chain, NFT_MSG_DELCHAIN,
> + family);
> + kfree(old_chain);
> + nf_tables_chain_notify(skb, nlh, table, new_chain, NFT_MSG_NEWCHAIN,
> + family);
> + return 0;
> +}
> +
> static int nf_tables_newchain(struct sock *nlsk, struct sk_buff *skb,
> const struct nlmsghdr *nlh,
> const struct nlattr * const nla[])
> @@ -714,7 +770,7 @@ static int nf_tables_newchain(struct sock *nlsk, struct sk_buff *skb,
> if (nlh->nlmsg_flags & NLM_F_EXCL)
> return -EEXIST;
> if (nlh->nlmsg_flags & NLM_F_REPLACE)
> - return -EOPNOTSUPP;
> + return nf_tables_mvchain(skb, nlh, table, chain, nla);
>
> if ((chain->flags & NFT_BASE_CHAIN) && nla[NFTA_CHAIN_POLICY]) {
> return nf_tables_chain_policy(chain,
> --
> 1.7.12.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-10-31 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 9:28 [nf-next/nf_tables-experiments - PATCH 0/2] chain rename and rule replacement Tomasz Bursztyka
2012-10-31 9:28 ` [nf-next/nf_tables-experiments - PATCH 1/2] nf_tables: Add support for changing users chain's name Tomasz Bursztyka
2012-10-31 13:49 ` Pablo Neira Ayuso [this message]
2012-10-31 14:29 ` Tomasz Bursztyka
2012-10-31 15:38 ` Pablo Neira Ayuso
2012-10-31 9:28 ` [nf-next/nf_tables-experiments - PATCH 2/2] nf_tables: Add support for replacing a rule by another one 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=20121031134924.GA1060@1984 \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=tomasz.bursztyka@linux.intel.com \
/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).