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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <95092268-54c9-4e22-8ccf-8f3f1eb266d0@email.android.com>
Date:	Wed, 31 Mar 2010 20:16:05 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	James Morris <jmorris@...ei.org>
CC:	Ingo Molnar <mingo@...e.hu>, 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

OK... I think I'm going to write this up as unconfirmed... which means the only known problem that was not addressed in rc3 is the 32-bit NUMA issue, which we have a bug for.

Linus: does this address your concerns for now, or do you still want us to revert?

"James Morris" <jmorris@...ei.org> wrote:

>On Wed, 31 Mar 2010, H. Peter Anvin wrote:
>
>> On 03/31/2010 04:43 PM, James Morris wrote:
>> >>
>> >> Upgraded how?  The problem no longer happens?
>> > 
>> > Upgraded to the latest rawhide userland -- I have not since tested with 
>> > bootmem off.  I'll try and do so again when I get a chance.
>> > 
>> 
>> That would be great.  The sooner the better, obviously.
>
>I'm not seeing any problems now, with current Linus and rawhide.  I'll 
>leave bootmem off and see if anything comes up again.
>
>
>-- 
>James Morris
><jmorris@...ei.org>

--
Sent from my mobile phone, pardon any lack of formatting.