From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Kirill Tkhai <ktkhai@parallels.com>
Cc: netfilter-devel@vger.kernel.org,
Patrick McHardy <kaber@trash.net>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
tkhai@yandex.ru, Pavel Emelyanov <xemul@parallels.com>
Subject: Re: [PATCH] ipt_CLUSTERIP: Add network device notifier
Date: Wed, 11 Jun 2014 13:49:57 +0200 [thread overview]
Message-ID: <20140611114957.GA23352@localhost> (raw)
In-Reply-To: <1402487079.32126.54.camel@tkhai>
On Wed, Jun 11, 2014 at 03:44:39PM +0400, Kirill Tkhai wrote:
> Hi, Pablo,
>
> В Пн, 28/04/2014 в 16:23 +0200, Pablo Neira Ayuso пишет:
> > Hi,
> >
> > On Mon, Apr 07, 2014 at 03:58:49PM +0400, Kirill Tkhai wrote:
> > > Clusterip target does dev_hold() in .checkentry, while dev_put() in .destroy.
> > > So, unregister_netdevice catches the leak:
> > >
> > > # modprobe dummy
> > > # iptables -A INPUT -d 10.31.3.236 -j CLUSTERIP --new --hashmode sourceip -i dummy0 --clustermac 01:aa:7b:47:f7:d7 --total-nodes 2 --local-node 1
> > > # rmmod dummy
> > >
> > > Message from syslogd@localhost ...
> > > kernel: unregister_netdevice: waiting for dummy0 to become free. Usage count = 1
> > >
> > [...]
> > > 1 file changed, 134 insertions(+), 12 deletions(-)
> >
> > I have spinned several times on this patch, and I'm not very happy
> > with taking this fix:
> >
> > 1) It's quite large fix for a situation that seems unlikely to me.
>
> We have several reports from containers users, who bumped into this.
> The hang happens on netns stop, it's 100% reproducible. Every time
> a container is stopping or a device is going away, the unregistration
> fails and hungs if CLUSTERIP is used. So, we'd want to have some fix
> of this.
How it this combination being triggered there? I mean:
# modprobe dummy
# iptables -A INPUT -d 10.31.3.236 -j CLUSTERIP ...
# rmmod dummy
Is it something included in some scripts that automate the setup?
--
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:[~2014-06-11 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 11:58 [PATCH] ipt_CLUSTERIP: Add network device notifier Kirill Tkhai
2014-04-28 14:23 ` Pablo Neira Ayuso
2014-06-11 11:44 ` Kirill Tkhai
2014-06-11 11:49 ` Pablo Neira Ayuso [this message]
2014-06-11 11:55 ` Kirill Tkhai
2014-06-11 11:58 ` Pavel Emelyanov
2014-06-11 12:03 ` Kirill Tkhai
2014-06-11 12:10 ` Pavel Emelyanov
2014-06-11 12:00 ` Pablo Neira Ayuso
2014-06-11 12:10 ` Kirill Tkhai
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=20140611114957.GA23352@localhost \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=ktkhai@parallels.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=tkhai@yandex.ru \
--cc=xemul@parallels.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).