linux-kernel - Re: [PATCH 2/2] linux: ARM: memmap: Revise freeing unused memmap entries for SPARSEMEM

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120329121313.GF22414@n2100.arm.linux.org.uk>
Date:	Thu, 29 Mar 2012 13:13:14 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Akira Takeuchi <takeuchi.akr@...panasonic.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] linux: ARM: memmap: Revise freeing unused memmap
	entries for SPARSEMEM

On Thu, Mar 29, 2012 at 07:02:52PM +0900, Akira Takeuchi wrote:
> F0-F4 is the unused memory regions and their corresponding memmap entries
> can be freed. However, free_unused_memmap() only frees the entries for
> F1/F2/F4, and does not free the entries for F0/F3.

No we're not going to support having free areas at the start of an
otherwise populated bank of memory.  This is just insane.  Fix your
hardware instead or your sparsemem setup.
--
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/