From: Andrew Morton <akpm@linux-foundation•org>
To: ebiederm@xmission•com (Eric W. Biederman)
Cc: torvalds@linux-foundation•org, sfr@canb•auug.org.au,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
yhlu.kernel@gmail•com, ink@jurassic•park.msu.ru,
jbarnes@virtuousgeek•org, netdev@vger•kernel.org,
viro@zeniv•linux.org.uk, dwmw2@infradead•org, sam@ravnborg•org,
johnstul@us•ibm.com, tglx@linutronix•de
Subject: Re: linux-next: Tree for September 3
Date: Thu, 4 Sep 2008 13:41:48 -0700 [thread overview]
Message-ID: <20080904134148.0fde4508.akpm@linux-foundation.org> (raw)
In-Reply-To: <m163pb4pru.fsf@frodo.ebiederm.org>
On Thu, 04 Sep 2008 13:31:01 -0700
ebiederm@xmission•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.
next prev parent reply other threads:[~2008-09-04 20:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080903191619.6b6b230e.sfr@canb.auug.org.au>
[not found] ` <20080903214634.ea17ff53.akpm@linux-foundation.org>
[not found] ` <alpine.LFD.1.10.0809032201510.3378@nehalem.linux-foundation.org>
[not found] ` <20080903223318.84b6ce8b.akpm@linux-foundation.org>
[not found] ` <alpine.LFD.1.10.0809040045190.3378@nehalem.linux-foundation.org>
[not found] ` <20080904012544.cabed847.akpm@linux-foundation.org>
[not found] ` <alpine.LFD.1.10.0809040143350.3452@nehalem.linux-foundation.org>
[not found] ` <20080904015701.5959623a.akpm@linux-foundation.org>
[not found] ` <alpine.LFD.1.10.0809040203510.3452@nehalem.linux-foundation.org>
2008-09-04 17:45 ` linux-next: Tree for September 3 Andrew Morton
2008-09-04 18:05 ` Linus Torvalds
2008-09-04 18:34 ` Andrew Morton
2008-09-04 20:31 ` Eric W. Biederman
2008-09-04 20:41 ` Andrew Morton [this message]
2008-09-04 21:03 ` Eric W. Biederman
2008-09-04 22:22 ` Andrew Morton
2008-09-04 22:45 ` Thomas Gleixner
2008-09-04 23:17 ` Linus Torvalds
2008-09-05 5:39 ` Arjan van de Ven
2008-09-04 23:17 ` Andrew Morton
2008-09-04 23:25 ` Linus Torvalds
2008-09-04 23:27 ` Thomas Gleixner
2008-09-05 11:04 ` Ingo Molnar
2008-09-05 17:49 ` Andrew Morton
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=20080904134148.0fde4508.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=dwmw2@infradead$(echo .)org \
--cc=ebiederm@xmission$(echo .)com \
--cc=ink@jurassic$(echo .)park.msu.ru \
--cc=jbarnes@virtuousgeek$(echo .)org \
--cc=johnstul@us$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sam@ravnborg$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=yhlu.kernel@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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