linux-kernel - Re: PATCH] mm: Use alloc_bootmem_node

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:	Fri, 6 May 2011 15:39:14 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Stefan Hellermann <stefan@...2masters.de>,
	linux-kernel@...r.kernel.org
Subject: Re: PATCH] mm: Use alloc_bootmem_node_nopanic on really needed path

On Fri, 06 May 2011 15:29:41 -0700
Yinghai Lu <yinghai@...nel.org> wrote:

> Stefan found nobootmem does not work on his system that only have 8M ram.

What does "does not work" mean?  From the patch, it appears that the
machine paniced?

This is important because without a recognisable description of the
failure it is hard for people to determine whether your patch might fix
a problem which they are observing.

The patch applies to 2.6.36, 37 and 38 (at least).  Do you think it
should be backported?  If so, how far back in time is it applicable?

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