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

Message-ID: <AANLkTimcCuhtEguCZsVmfAaCDYrGOeJB7+O=EziJ59rR@mail.gmail.com>
Date:	Fri, 1 Apr 2011 10:31:57 -0700
From:	Kevin Cernekee <cernekee@...il.com>
To:	David Daney <ddaney@...iumnetworks.com>,
	Ralf Baechle <ralf@...ux-mips.org>
Cc:	Michael Sundius <msundius@...co.com>,
	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 Fri, Apr 1, 2011 at 9:56 AM, David Daney <ddaney@...iumnetworks.com> 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.

I noticed that some of the other architectures have started using the
<linux/memblock.h> APIs for memory setup.  Do you think this would be
useful on MIPS, as part of a larger refactoring of bootmem_init() ?

What I liked about Michael's fix was that it is simple and
straightforward enough to meet the stable tree criteria.  Long term it
would probably be a good idea to clean up the memory init code and get
rid of the cut&paste "for" loops.
--
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/