netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next 0/3] netfilter: clusterip: don't register hook in all netns
Date: Sun, 1 Aug 2021 11:46:31 +0200	[thread overview]
Message-ID: <20210801094631.GA15328@salvia> (raw)
In-Reply-To: <20210722084834.27027-1-fw@strlen.de>

On Thu, Jul 22, 2021 at 10:48:31AM +0200, Florian Westphal wrote:
> This series stops ipt_CLUSTERIP from registering arp mangling hook
> unconditionally.
> 
> Hook gets installed/removed from checkentry/destroy callbacks.
> 
> Before this, modprobe ipt_CLUSTERIP would add a hook in each netns.
> While at it, also get rid of x_tables.h/xt storage space in struct net,
> there is no need for this.

Series applied, thanks.

I made a small update to 2/3 here:

@@ -517,6 +531,19 @@ static int clusterip_tg_check(const struct xt_tgchk_param *par)
                return ret;
        }

+       if (cn->hook_users == 0) {
+               ret = nf_register_net_hook(par->net, &cip_arp_ops);
+
+               if (ret < 0) {
+                       clusterip_config_entry_put(config); <--
+                       clusterip_config_put(config); <--

to use config instead cipinfo->config which is set on later.

      parent reply	other threads:[~2021-08-01  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22  8:48 [PATCH nf-next 0/3] netfilter: clusterip: don't register hook in all netns Florian Westphal
2021-07-22  8:48 ` [PATCH nf-next 1/3] netfilter: ipt_CLUSTERIP: only add arp mangle hook when required Florian Westphal
2021-07-22  8:48 ` [PATCH nf-next 2/3] netfilter: ipt_CLUSTERIP: use clusterip_net to store pernet warning Florian Westphal
2021-07-22  8:48 ` [PATCH nf-next 3/3] netfilter: remove xt pernet data Florian Westphal
2021-08-01  9:46 ` 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=20210801094631.GA15328@salvia \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --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).