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]
Date:	Thu, 04 Dec 2008 13:11:20 -0500
From:	Stephen Smalley <sds@...ho.nsa.gov>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	"Kok, Auke" <auke-jan.h.kok@...el.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	ebiederm@...ssion.com, James Morris <jmorris@...ei.org>,
	Eric Paris <eparis@...isplace.org>
Subject: Re: [E1000-devel] networking probs in next-20081203

On Thu, 2008-12-04 at 20:52 +0300, Alexey Dobriyan wrote:
> On Thu, Dec 04, 2008 at 09:41:24AM -0800, Kok, Auke wrote:
> > Alexey Dobriyan wrote:
> > > On Wed, Dec 03, 2008 at 05:18:34PM -0800, Andrew Morton wrote:
> > >> x86_64, CONFIG_E1000E=y.
> > >>
> > >> Current Linus mainline is OK, but with linux-next I'm seeing the following:
> > >>
> > >> - During boot I see a "cannot open /proc/net/dev" fly past.  But when
> > >>   it gets to the login prompt, I can read /proc/net/dev.
> > > 
> > > I _suspect_ it might me something with /proc/net changes (again) and initcall
> > > ordering.
> > > 
> > > Andrew, as rejectless quick test, you can do
> > > 
> > > 	git checkout -f 26b0d981e7dd1d5b4852ed5719bd1388c7994163	# sic
> > > 
> > > which is the last tree merged before proc tree in that next tree.
> > > 
> > >> - Networking won't come up.  `ifup eth0' says "determining ip address
> > >>   ...  failed", and the failure is immediate.
> > >>
> > >> - eth0 appears in the ifconfig oputput as normal - it just won't come up.
> > >>
> > >> - nothing interesting in dmesg
> > >>
> > >>
> > >> Here's the dmesg: http://userweb.kernel.org/~akpm/dmesg-dead-net.txt
> > >> (that dmesg was generated with E1000=y, E1000E=y, but that doesn't seem
> > >> to matter)
> > >>
> > >> The .config: http://userweb.kernel.org/~akpm/config-dead-net.txt
> > 
> > perhaps this line has something to do with it?
> > 
> > [   50.539326] type=1400 audit(1228348149.537:4): avc:  denied  { mount } for
> > pid=11636 comm="ifconfig" name="/" dev=proc/net ino=4026531842
> > scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:object_r:unlabeled_t:s0
> > tclass=filesystem

The significant line from the dmesg output is this:
[   32.113405] SELinux: initialized (dev proc/net, type proc/net), not configured for labeling

> Of course!
> 
> > maybe try disabling selinux?
> 
> This will work. :^)

SELinux didn't change here.  /proc/net did.

-- 
Stephen Smalley
National Security Agency

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ