From: Xin Long <lucien.xin@gmail.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
netfilter-devel@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [Patch net] ipt_CLUSTERIP: fix a race condition of proc file creation
Date: Thu, 8 Feb 2018 19:45:05 +0800 [thread overview]
Message-ID: <CADvbK_d6io1+frrWfnB8ziYGZDYs_u9JTbT7n2HQPHt6vz2nUg@mail.gmail.com> (raw)
In-Reply-To: <20180208055918.20411-1-xiyou.wangcong@gmail.com>
On Thu, Feb 8, 2018 at 1:59 PM, Cong Wang <xiyou.wangcong@gmail.com> wrote:
> There is a race condition between clusterip_config_entry_put()
> and clusterip_config_init(), after we release the spinlock in
> clusterip_config_entry_put(), a new proc file with a same IP could
> be created immediately since it is already removed from the configs
> list, therefore it triggers this warning:
>
> ------------[ cut here ]------------
> proc_dir_entry 'ipt_CLUSTERIP/172.20.0.170' already registered
> WARNING: CPU: 1 PID: 4152 at fs/proc/generic.c:330 proc_register+0x2a4/0x370 fs/proc/generic.c:329
> Kernel panic - not syncing: panic_on_warn set ...
>
> As a quick fix, just move the proc_remove() inside the spinlock.
>
> Reported-by: <syzbot+03218bcdba6aa76441a3@syzkaller.appspotmail.com>
> Fixes: 6c5d5cfbe3c5 ("netfilter: ipt_CLUSTERIP: check duplicate config when initializing")
> Tested-by: Paolo Abeni <pabeni@redhat.com>
> Cc: Xin Long <lucien.xin@gmail.com>
> Cc: Pablo Neira Ayuso <pablo@netfilter.org>
> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
> ---
> net/ipv4/netfilter/ipt_CLUSTERIP.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/net/ipv4/netfilter/ipt_CLUSTERIP.c b/net/ipv4/netfilter/ipt_CLUSTERIP.c
> index 3a84a60f6b39..1ff72b87a066 100644
> --- a/net/ipv4/netfilter/ipt_CLUSTERIP.c
> +++ b/net/ipv4/netfilter/ipt_CLUSTERIP.c
> @@ -107,12 +107,6 @@ clusterip_config_entry_put(struct net *net, struct clusterip_config *c)
>
> local_bh_disable();
> if (refcount_dec_and_lock(&c->entries, &cn->lock)) {
> - list_del_rcu(&c->list);
> - spin_unlock(&cn->lock);
> - local_bh_enable();
> -
> - unregister_netdevice_notifier(&c->notifier);
> -
> /* In case anyone still accesses the file, the open/close
> * functions are also incrementing the refcount on their own,
> * so it's safe to remove the entry even if it's in use. */
> @@ -120,6 +114,12 @@ clusterip_config_entry_put(struct net *net, struct clusterip_config *c)
> if (cn->procdir)
> proc_remove(c->pde);
> #endif
> + list_del_rcu(&c->list);
> + spin_unlock(&cn->lock);
> + local_bh_enable();
> +
> + unregister_netdevice_notifier(&c->notifier);
> +
> return;
> }
> local_bh_enable();
> --
> 2.13.0
>
Reviewed-by: Xin Long <lucien.xin@gmail.com>
next prev parent reply other threads:[~2018-02-08 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 5:59 [Patch net] ipt_CLUSTERIP: fix a race condition of proc file creation Cong Wang
2018-02-08 5:59 ` [Patch net] ipt_CLUSTERIP: fix a refcount bug in clusterip_config_find_get() Cong Wang
2018-02-08 8:01 ` Florian Westphal
2018-02-08 20:05 ` Cong Wang
2018-02-08 11:45 ` Xin Long [this message]
2018-02-08 16:58 ` [Patch net] ipt_CLUSTERIP: fix a race condition of proc file creation Pablo Neira Ayuso
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=CADvbK_d6io1+frrWfnB8ziYGZDYs_u9JTbT7n2HQPHt6vz2nUg@mail.gmail.com \
--to=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=xiyou.wangcong@gmail.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).