[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1sk6oky96.fsf@fess.ebiederm.org>
Date: Wed, 21 Apr 2010 19:38:13 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Ben Hutchings <ben@...adent.org.uk>
Cc: Martín Ferrari <martin.ferrari@...il.com>,
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
Ben Hutchings <ben@...adent.org.uk> writes:
> On Wed, 2010-04-21 at 12:36 -0700, Eric W. Biederman wrote:
>> 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?
>
> Yes, but not many beyond the stable updates, and nothing in this area.
> You can see the list at:
> http://svn.debian.org/wsvn/kernel/dists/trunk/linux-2.6/debian/patches/series/base
Then I should ask what is startns?
Either that is doing something different from my equivalent program, or I have
patches to fix this, that just haven't been merged yet.
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
Powered by blists - more mailing lists