linux-kernel - Re: [PATCH -mm 11/14] bootmem: respect goal more likely

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

Date:	Thu, 05 Jun 2008 10:22:52 +0200
From:	Johannes Weiner <hannes@...urebad.de>
To:	Yasunori Goto <y-goto@...fujitsu.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm 11/14] bootmem: respect goal more likely

Hi,

Yasunori Goto <y-goto@...fujitsu.com> writes:

> Hi.
>
>> >> 
>> >> Could you boot a working image with bootmem_debug in the command line?
>> >> Perhaps seeing the usual bootmem usage on this box gives a hint what is
>> >> broken.
>> >
>> > Ok. I'll try it.
>> 
>> Thanks!
>
> I attached bootmem log with related message. 
> If you realize anything, please let me know.
>
> Note: 
>   In this hardware configuration, node 1 to 16 are "memory less" node.
>   They may be hot-added later.
>   So, there are some messages of "no start_pfn".
>   But, for_each_loop of bootmem skips them because ia64 kernel checks
>   "memory less" node and skip to call init_bootmem_node().
>   I think it is not cause.

Thank you very much.  I think I spotted the bug and will provide an
explanation and a patch when I am awake again.

	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/