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:	Mon, 30 Oct 2006 23:22:41 -0800
From:	Greg KH <gregkh@...e.de>
To:	Mike Galbraith <efault@....de>
Cc:	"Martin J. Bligh" <mbligh@...gle.com>,
	Cornelia Huck <cornelia.huck@...ibm.com>,
	Andy Whitcroft <apw@...dowen.org>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	Steve Fox <drfickle@...ibm.com>
Subject: Re: 2.6.19-rc3-mm1 -- missing network adaptors

On Tue, Oct 31, 2006 at 08:09:54AM +0100, Mike Galbraith wrote:
> On Mon, 2006-10-30 at 22:59 -0800, Greg KH wrote:
> > On Mon, Oct 30, 2006 at 10:37:47PM -0800, Martin J. Bligh wrote:
> > > Mike Galbraith wrote:
> > > >On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
> > > >
> > > >>Maybe the initscripts have problems coping with the new layout
> > > >>(symlinks instead of real devices)?
> > > >
> > > >SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
> > > >follow symlinks (bounces off symlink and does nutty stuff instead).  If
> > > >any of the boxen you're having troubles with use libsysfs in their init
> > > >stuff, that's likely the problem.
> > > 
> > > If that is what's happening, then the problem is breaking previously
> > > working boxes by changing a userspace API. I don't know exactly which
> > > patch broke it, but reverting all Greg's patches (except USB) from
> > > -mm fixes the issue.
> > 
> > Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> > all work just fine.  Doesn't anyone read the Kconfig help entries for
> > new kernel options?
> 
> That's terminal here atm:  kernel BUG at arch/i386/mm/pageattr.c:165!
> 
> I did have it set, but had to disable it to not panic.

I think there are two different issues here.  That kernel config option
should not be causing an oops in mm code.

Can you bisect the different patches to see which one causes the
problem?

thanks,

greg k-h
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ