[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080904134148.0fde4508.akpm@linux-foundation.org>
Date: Thu, 4 Sep 2008 13:41:48 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: ebiederm@...ssion.com (Eric W. Biederman)
Cc: torvalds@...ux-foundation.org, sfr@...b.auug.org.au,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
yhlu.kernel@...il.com, ink@...assic.park.msu.ru,
jbarnes@...tuousgeek.org, netdev@...r.kernel.org,
viro@...iv.linux.org.uk, dwmw2@...radead.org, sam@...nborg.org,
johnstul@...ibm.com, tglx@...utronix.de
Subject: Re: linux-next: Tree for September 3
On Thu, 04 Sep 2008 13:31:01 -0700
ebiederm@...ssion.com (Eric W. Biederman) wrote:
> >> > config: http://userweb.kernel.org/~akpm/config-sony.txt
> >> > dmesg: http://userweb.kernel.org/~akpm/dmesg-sony-without.txt
> >>
> >> That whole thing should just be a simple symlink:
> >>
> >> fs/proc/proc_net.c: proc_symlink("net", NULL, "self/net");
> >
> > /proc/self/net looks fine.
> >
> >> are you sure it's a plain tree of mine, without any of the patches
> >> floating around between Eric/Al?
> >
> > yup, it's yesterday's mainline.
>
> Does the problem happen if you disable selinux?
>
> This feels like a case of selinux being over zealous.
yeah, adding `selinux=0' to the boot command line fixes it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists