Messages in this thread | | | Date | Thu, 21 Oct 2010 17:15:32 +0200 | From | Michael Leun <> | Subject | Re: NET_NS: unregister_netdevice: waiting for lo to become free (adding ipv6 address to interface) |
| |
Hi,
unfortunately the bug described below originally reported in 2.6.35-rcX is still there in 2.6.36.
Is there anything I might do to help fix it (besides fixing it myself, I do not have the knowhow)?
On Thu, 5 Aug 2010 13:47:07 +0200 Michael Leun <lkml20100708@newton.leun.net> wrote:
[...] > Putting an ipv6 address on a device seems to be the trigger: > > OrigNS > # ip link add type veth > OrigNS > # ip link set dev veth0 up > OrigNS > # unshare -n /bin/bash > NewNS > # echo $$ > <SomePID> > OrigNS > # ip link set dev veth1 netns <SomePID> # this, of course is > on a different terminal NewNS > # ip link set dev veth1 up > NewNS > # ip -6 addr add dev veth1 fd50:dead:beef::1/64 > NewNS > # exit > > Yields > > kernel: unregister_netdevice: waiting for veth1 to become free. Usage > count = 3 > > Oh - its veth1 this time, not lo - add an "ip link set up dev lo" in > the above scenario just after the unshare, and you get the message > with lo. > > One might ask, if > > > # unshare -n /bin/bash > > # ip link set up dev lo > > # ip -6 addr add dev veth1 fd50:dead:beef::1/64 > > # exit > > also does the trick, so I tried it - and it does NOT. > > In the above scenario, not setting veth0 and veth1 up also makes it > not happen. Only setting veth1 up also is not enough (seems to need > to be "really up" what as you shurely know with veth is only the case > when both sides are up). > > I hope, this makes it somewhat easier to track that down.
-- MfG,
Michael Leun
| |