Martín Ferrari <[email protected]> writes: > I'm not starting a new thread/bug, as this is probably related... > > I just discovered that in 2.6.33, if I create a veth inside a > namespace and then move one of the halves into the main namespace, > when I kill the namespace, I get one of these warnings followed by an > oops. This does not happen if the veth is created from the main ns and > then moved, nor in 2.6.32. This happens both in Qemu and on real > hardware (both amd64) > > To reproduce: > > $ sudo ./startns bash > # ip l a type veth > # ip l s veth0 netns 1 > # exit
Nasty weird. I did a quick test here, and I'm not seeing that. Does the 2.6.33 experimental kernel have any patches applied? The sysfs_add_one path looks like someone we hit a duplicate name, which is a bug of an entirely different kind. From there it appears that we later destroy the device not realizing it isn't in sysfs. Which causes everything to explode. The sysctl issues appears to be that somewhere we have the ordering of creates and/or deletes wrong. It is just possible the changes for batch deletion might be exposing a bug under load. The sysctl error appears to be in the class of things that should never happen but that we should handle correctly anyway. Eric -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
