linux-kernel - Re: [PATCH] memblock: Fix big size with find

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] [day] [month] [year] [list]

Date:	Wed, 06 Oct 2010 15:47:57 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Yinghai Lu <yinghai@...nel.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] memblock: Fix big size with find_region()

On 10/06/2010 03:45 PM, Andrew Morton wrote:
> 
> whomeidunno.  The question is "is this something we want to know
> about".  If it's a BIOS/acpi/whatever error then I'd think "yes",
> because that would then lead to useful kernel workarounds or BIOS
> updates?

I don't think it's inherently that... it could be in some cases, but not
in others.  In either case, an allocation failure should be handled in
the calling layer... or we have a much more serious problem.

However, I suspect the most common case where we'll hit this is when
something wants to fit inside a chunk where it simply doesn't fit ...
and it'll either move on to the next plausible chunk or fail at that point.

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