linux-kernel - Re: Config NO_BOOTMEM breaks my amd64 box

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, 1 Apr 2010 09:58:03 +1100 (EST)
From:	James Morris <jmorris@...ei.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
	linux-kernel@...r.kernel.org, airlied@...ux.ie,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: Config NO_BOOTMEM breaks my amd64 box

On Wed, 31 Mar 2010, Ingo Molnar wrote:

> > 
> > Yes, it was happening with -rc3.
> 
> Could you please send the bootlog that Yinghai asked for, plus also one that 
> you get with NO_BOOTMEM turned off (for comparison)?

I don't have the old boot logs, and have since upgraded the system 
further.  

IIRC, the boot was failing after not being able to find the root fs 
(ext3/lvm/raid0).  I thought it was a dracut issue, but it seemed to be 
fixed by enabling bootmem.

> Also, when did you first hit this bug? This code has been upstream for almost 
> a month, and it was in linux-next before that - so you should have hit this 
> much sooner. A rough timeframe would suffice. I suppose you were booting 
> upstream kernels during the merge window as well?

In this case, in the last few days (also when I first saw or noticed the 
bootmem option).  I was booting relatively recent linus kernels during the 
merge window, although my main work was being done on an older upstream 
kernel.

-- 
James Morris
<jmorris@...ei.org>
--
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/