netdev - Re: Bug#577640: linux-image-2.6.33-2-amd64: Kernel warnings in netns thread

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <m1ljcgzjh4.fsf@fess.ebiederm.org>
Date:	Wed, 21 Apr 2010 12:36:07 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Martín Ferrari <martin.ferrari@...il.com>
Cc:	Ben Hutchings <ben@...adent.org.uk>, 577640@...s.debian.org,
	netdev <netdev@...r.kernel.org>,
	"Eric W. Biederman" <ebiederm@...stanetworks.com>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Mathieu Lacage <mathieu.lacage@...hia.inria.fr>
Subject: Re: Bug#577640: linux-image-2.6.33-2-amd64: Kernel warnings in netns  thread

Martín Ferrari <martin.ferrari@...il.com> 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 from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html