From: "Martín Ferrari" <martin.ferrari@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
577640@bugs.debian.org, netdev <netdev@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@aristanetworks.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Mathieu Lacage <mathieu.lacage@sophia.inria.fr>
Subject: Re: Bug#577640: linux-image-2.6.33-2-amd64: Kernel warnings in netns thread
Date: Thu, 22 Apr 2010 16:05:13 +0200 [thread overview]
Message-ID: <y2kb9800b71004220705s4db40c4csb3923b61f9ae8321@mail.gmail.com> (raw)
In-Reply-To: <m1sk6oky96.fsf@fess.ebiederm.org>
On Thu, Apr 22, 2010 at 04:38, Eric W. Biederman <ebiederm@xmission.com> wrote:
>>> > $ sudo ./startns bash
>>> > # ip l a type veth
>>> > # ip l s veth0 netns 1
>>> > # exit
> Then I should ask what is startns?
That's just a simple C program that calls unshare(CLONE_NEWNET) and
execs a shell.
> Either that is doing something different from my equivalent program, or I have
> patches to fix this, that just haven't been merged yet.
I have just downloaded and compiled 2.6.32-2 and 2.6.34-rc5 from
kernel.org using the .config from the debian package, and the oops is
reproducible in both.
This small C file reproduces the error every time:
$ cat netnsoops.c
#include <stdio.h>
#include <stdlib.h>
#define _GNU_SOURCE
#include <sched.h>
int main(int argc, char *argv[])
{
int c;
unsigned long flags = CLONE_NEWNET;
if(unshare(flags) == -1) {
perror("unshare");
return 1;
}
system("ip link add name FOO type veth peer name BAR");
system("ip link set FOO netns 1");
system("ip link show");
return 0;
}
--
Martín Ferrari
prev parent reply other threads:[~2010-04-22 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100413112017.8505.36380.reportbug@japot.localdomain>
2010-04-18 17:33 ` Bug#577640: linux-image-2.6.33-2-amd64: Kernel warnings in netns thread Ben Hutchings
2010-04-21 15:19 ` Martín Ferrari
2010-04-21 19:36 ` Eric W. Biederman
2010-04-22 0:14 ` Ben Hutchings
2010-04-22 2:38 ` Eric W. Biederman
2010-04-22 14:05 ` Martín Ferrari [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=y2kb9800b71004220705s4db40c4csb3923b61f9ae8321@mail.gmail.com \
--to=martin.ferrari@gmail.com \
--cc=577640@bugs.debian.org \
--cc=adobriyan@gmail.com \
--cc=ben@decadent.org.uk \
--cc=ebiederm@aristanetworks.com \
--cc=ebiederm@xmission.com \
--cc=mathieu.lacage@sophia.inria.fr \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).