netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: fgao@ikuai8.com
Cc: netfilter-devel@vger.kernel.org, gfree.wind@gmail.com
Subject: Re: [PATCH nf-next 1/1] netfilter: nf_tables: Eliminate duplicated codes in nf_tables_table_enable
Date: Wed, 18 Jan 2017 20:55:52 +0100	[thread overview]
Message-ID: <20170118195552.GA14768@salvia> (raw)
In-Reply-To: <1484023359-30227-1-git-send-email-fgao@ikuai8.com>

On Tue, Jan 10, 2017 at 12:42:39PM +0800, fgao@ikuai8.com wrote:
> From: Gao Feng <fgao@ikuai8.com>
> 
> When something failed in nf_tables_table_enable, it would unregister
> the chains. But the rollback codes are same as nf_tables_table_disable
> almostly, except there is one counter check.
> Now create one wrapper function to eliminate the duplicated codes.
> 
> Signed-off-by: Gao Feng <fgao@ikuai8.com>
> ---
>  net/netfilter/nf_tables_api.c | 47 ++++++++++++++++++++++---------------------
>  1 file changed, 24 insertions(+), 23 deletions(-)
> 
> diff --git a/net/netfilter/nf_tables_api.c b/net/netfilter/nf_tables_api.c
> index a019a87..28a0bd7 100644
> --- a/net/netfilter/nf_tables_api.c
> +++ b/net/netfilter/nf_tables_api.c
> @@ -576,6 +576,27 @@ static int nf_tables_gettable(struct net *net, struct sock *nlsk,
>  	return err;
>  }
>  
> +static void _nf_tables_table_disable(struct net *net,
> +				     const struct nft_af_info *afi,
> +				     struct nft_table *table,
> +				     u32 cnt)
> +{
> +	struct nft_chain *chain;
> +
> +	list_for_each_entry(chain, &table->chains, list) {
> +		if (!nft_is_active_next(net, chain))
> +			continue;
> +		if (!(chain->flags & NFT_BASE_CHAIN))
> +			continue;
> +
> +		if (cnt-- == 0)
> +			break;
> +
> +		nf_unregister_net_hooks(net, nft_base_chain(chain)->ops,
> +					afi->nops);
> +	}
> +}
> +
>  static int nf_tables_table_enable(struct net *net,
>  				  const struct nft_af_info *afi,
>  				  struct nft_table *table)
> @@ -598,18 +619,8 @@ static int nf_tables_table_enable(struct net *net,
>  	}
>  	return 0;
>  err:
> -	list_for_each_entry(chain, &table->chains, list) {
> -		if (!nft_is_active_next(net, chain))
> -			continue;
> -		if (!(chain->flags & NFT_BASE_CHAIN))
> -			continue;
> -
> -		if (i-- <= 0)
> -			break;
> -
> -		nf_unregister_net_hooks(net, nft_base_chain(chain)->ops,
> -					afi->nops);
> -	}
> +	if (i)
> +		_nf_tables_table_disable(net, afi, table, i);
>  	return err;
>  }
>  
> @@ -617,17 +628,7 @@ static void nf_tables_table_disable(struct net *net,
>  				    const struct nft_af_info *afi,
>  				    struct nft_table *table)
>  {
> -	struct nft_chain *chain;
> -
> -	list_for_each_entry(chain, &table->chains, list) {
> -		if (!nft_is_active_next(net, chain))
> -			continue;
> -		if (!(chain->flags & NFT_BASE_CHAIN))
> -			continue;
> -
> -		nf_unregister_net_hooks(net, nft_base_chain(chain)->ops,
> -					afi->nops);
> -	}
> +	_nf_tables_table_disable(net, afi, table, U32_MAX);
                                                  ^^^^^^^
While I think it's good to consolidate code, I don't like this.

Probably better something like this?

+static void nft_table_disable(struct net *net,
+                              const struct nft_af_info *afi,
+			       struct nft_table *table, int cnt)
+{
+	struct nft_chain *chain;
+
+	list_for_each_entry(chain, &table->chains, list) {
+		if (!nft_is_active_next(net, chain))
+			continue;
+		if (!(chain->flags & NFT_BASE_CHAIN))
+			continue;
+
+		nf_unregister_net_hooks(net, nft_base_chain(chain)->ops,
+					afi->nops);
+		if (cnt && --cnt == 0)
+			break;
+
+	}
+}

So you call:

        nft_table_disable(net, afi, table, 0);

      reply	other threads:[~2017-01-18 19:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10  4:42 [PATCH nf-next 1/1] netfilter: nf_tables: Eliminate duplicated codes in nf_tables_table_enable fgao
2017-01-18 19:55 ` Pablo Neira Ayuso [this message]

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=20170118195552.GA14768@salvia \
    --to=pablo@netfilter.org \
    --cc=fgao@ikuai8.com \
    --cc=gfree.wind@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 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).