linux-kernel - Re: [PATCH v2] bootmem: avoid freeing to bootmem after bootmem is done

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:	Mon, 27 Jul 2015 17:05:25 +0100
From:	Mel Gorman <mgorman@...e.de>
To:	Chris Metcalf <cmetcalf@...hip.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>,
	Pekka Enberg <penberg@...nel.org>,
	Paul McQuade <paulmcquad@...il.com>,
	Tang Chen <tangchen@...fujitsu.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] bootmem: avoid freeing to bootmem after bootmem is
 done

On Mon, Jul 27, 2015 at 11:36:06AM -0400, Chris Metcalf wrote:
> Bootmem isn't popular any more, but some architectures still use it,
> and freeing to bootmem after calling free_all_bootmem_core() can end
> up scribbling over random memory.  Instead, make sure the kernel
> generates a warning in this case by ensuring the node_bootmem_map
> field is non-NULL when are freeing or marking bootmem.
> 
> An instance of this bug was just fixed in the tile architecture
> ("tile: use free_bootmem_late() for initrd") and catching this case
> more widely seems like a good thing.
> 
> Signed-off-by: Chris Metcalf <cmetcalf@...hip.com>

Acked-by: Mel Gorman <mgorman@...e.de>

-- 
Mel Gorman
SUSE Labs
--
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/