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:	Wed, 16 Apr 2008 21:17:58 +0200
From:	Johannes Weiner <hannes@...urebad.de>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux MM <linux-mm@...ck.org>,
	Andi Kleen <andi@...stfloor.org>,
	Yasunori Goto <y-goto@...fujitsu.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Christoph Lameter <clameter@....com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Siddha\, Suresh B" <suresh.b.siddha@...el.com>
Subject: Re: [RFC][patch 2/5] mm: Node-setup agnostic free_bootmem()

Hi,

Ingo Molnar <mingo@...e.hu> writes:

> * Yinghai Lu <yhlu.kernel@...il.com> wrote:
>
>> >  Yes, it should work well with cross nodes case.
>> >
>> >  but please add boundary check on free_bootmem_node too.
>> 
>> also please note: it will have problem span nodes box.
>> 
>> for example: node 0: 0-2g, 4-6g, node1: 2-4g, 6-8g. and if ramdisk sit 
>> creoss 2G boundary. you will only free the range before 2g.
>
> yes. Such systems _will_ become more common - so the "this is rare" 
> arguments are incorrect. bootmem has to be robust enough to deal with 
> it.

Ingo, I never doubted any of this, I was just asking more than once if
and when this might happen.  And I don't want the allocator become
fragile, just not completely ignorant about bogus input.

But the situation is still not clear for me.  Ingo, how are these
node spanning pfn ranges represented in the kernel?  How many node
descriptors will you have in the case Yinghai described and how will
they look like?

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