linux-kernel - Re: [PATCH v2] MIPS: Kernel crashes on boot with SPARSEMEM + HIGHMEM enabled

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:	Fri, 01 Apr 2011 11:48:01 -0700
From:	David Daney <ddaney@...iumnetworks.com>
To:	Michael Sundius <msundius@...co.com>
CC:	Kevin Cernekee <cernekee@...il.com>,
	Ralf Baechle <ralf@...ux-mips.org>,
	David VomLehn <dvomlehn@...co.com>,
	Dave Hansen <dave@...ux.vnet.ibm.com>,
	Andy Whitcroft <apw@...dowen.org>,
	Jon Fraser <jfraser@...adcom.com>, linux-mips@...ux-mips.org,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [PATCH v2] MIPS: Kernel crashes on boot with SPARSEMEM + HIGHMEM
 enabled

On 04/01/2011 11:41 AM, Michael Sundius wrote:
> David Daney wrote:
>>
>>
>> I think this may do the same thing as my patch:
>>
>> http://patchwork.linux-mips.org/patch/1988/
>>
>> Although my patch had different motivations, and changes some other
>> things around too.
>>
>> David Daney
>>
> I'm not really sure why your kernel or initrd would be in memory was not
> within
> the range that had been accounted for. are you saying its in high mem?
>

Well the memory initialization code has a bunch of weird rules built in 
that prevent some memory from being used.

For example if the kernel resides in a different SPARSE page than the 
rest of memory bad things happen because memory_present() was not called 
on something that is later freed (when init memory is released).

If I try to put an initrd at a high physical address, the memory below 
that is not usable.

My three patches try to make some sense out of the whole thing.

David Daney

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