From: Kirill Tkhai <ktkhai@parallels.com>
To: Pavel Emelyanov <xemul@parallels.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
<netfilter-devel@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>,
"Jozsef Kadlecsik" <kadlec@blackhole.kfki.hu>, <tkhai@yandex.ru>
Subject: Re: [PATCH] ipt_CLUSTERIP: Add network device notifier
Date: Wed, 11 Jun 2014 16:03:15 +0400 [thread overview]
Message-ID: <1402488195.32126.70.camel@tkhai> (raw)
In-Reply-To: <53984482.5060309@parallels.com>
В Ср, 11/06/2014 в 15:58 +0400, Pavel Emelyanov пишет:
> On 06/11/2014 03:55 PM, Kirill Tkhai wrote:
>
> >> 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?
> >
> > It's a sample of how to trigger this. The problem is not in rmmod.
> >
> > Really it happens when container is stopping and device is going away.
> > It's not OpenVZ related, current LXC has the same problem.
>
> Then it should be reproducible with the help of simple 'unshare --net'
> plus 'ip link add ...' commands that would create netns and populate
> it with devices. Right?
Yes, exactly. It has to be triggered this way.
Thanks,
Kirill
--
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 12:03 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
2014-06-11 11:55 ` Kirill Tkhai
2014-06-11 11:58 ` Pavel Emelyanov
2014-06-11 12:03 ` Kirill Tkhai [this message]
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=1402488195.32126.70.camel@tkhai \
--to=ktkhai@parallels.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).