linux-kernel - Re: x86_64 account-for-memmap patch in 2.6.18-rc4-mm3 doesn't boot.

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]

Message-ID: <Pine.LNX.4.64.0609071502001.31287@skynet.skynet.ie>
Date:	Thu, 7 Sep 2006 15:16:59 +0100 (IST)
From:	Mel Gorman <mel@....ul.ie>
To:	Paul Jackson <pj@....com>
Cc:	Mel Gorman <mel@...net.ie>, linux-kernel@...r.kernel.org,
	akpm@...l.org, haveblue@...ibm.com, apw@...dowen.org, ak@....de,
	benh@...nel.crashing.org, paulus@...ba.org, kmannth@...il.com,
	tony.luck@...el.com, kamezawa.hiroyu@...fujitsu.com,
	y-goto@...fujitsu.com
Subject: Re: x86_64 account-for-memmap patch in 2.6.18-rc4-mm3 doesn't boot.

On Wed, 6 Sep 2006, Paul Jackson wrote:

> Mel Gorman wrote:
>> I could do with those lines, but I believe there was enough information
>> printed to determine why it failed to boot. I've attached a patch that
>> should boot the machine and assuming it works, I just need the output of
>> dmesg.
>
> Yup - that patch booted it, and produced the output you asked for.
>
> Here's the dmesg output from booting your patch:
>
> <dmesg log snipped>

Thanks. Now it's *painfully* obvious what went wrong - memmap is not 
necessarily in one zone and in your machine memmap spanned two zones. A 
patch will follow this mail that fixes the underlying issue but keeps the 
underflow check in case. Please give it a test if you get the chance. It 
passes regression tests here.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab
-
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/