[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160916120252.GA2384@toys.tundra.dog-lvm.novalocal>
Date: Fri, 16 Sep 2016 12:02:53 +0000
From: Anton Aksola <aakso@....fi>
To: Vadim Kochan <vadim4j@...il.com>
Cc: Nicolas Dichtel <nicolas.dichtel@...nd.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH v2] iproute2: build nsid-name cache only for commands
that need it
On Fri, Sep 16, 2016 at 02:25:40PM +0300, Vadim Kochan wrote:
> Anton, I just looked into tests after when I did post here. I am not
> sure it will be trivial,
> currently tests are running within separated network namespace by
> default (which I did) via
> 'unshare' tool, and now I see that it is better to call it explicitly
> from the each test case. So
> I am not sure netns related tests might be valid if they will be ran
> after 'unshare -n', if yes - then there is no problem, otherwise
> it needs to be fixed somehow - I will try to do this.
>
(excuse my duplicate emails if any received)
It seems that mounts made after 'unshare -n' will propagate back:
[root@...s iproute2]# ip netns
[root@...s iproute2]# unshare -n
[root@...s iproute2]# ip netns add foo
[root@...s iproute2]# ip netns exec foo ip link add type dummy
[root@...s iproute2]# exit
logout
[root@...s iproute2]# ip netns
foo
[root@...s iproute2]# ip netns exec foo ip link show dev dummy0
6: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT
link/ether ba:cc:6c:ca:2d:41 brd ff:ff:ff:ff:ff:ff
This doesn't seem to work with 'ip netns exec' as it makes sure mounts
do not propagate.
BR, Anton
Powered by blists - more mailing lists