linux-kernel - Re: bootmem allocator

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: <20080407190904.GH12292@elte.hu>
Date:	Mon, 7 Apr 2008 21:09:04 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Cyrill Gorcunov <gorcunov@...il.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: bootmem allocator


* Cyrill Gorcunov <gorcunov@...il.com> wrote:

> Hi Ingo, Peter,
> 
> small question. It was a patch recently posted which removes memset(x, 
> 0, x) after __alloc_bootmem call. There are a few another code 
> snippets who still call memset(x, 0, x). And who is responsible for 
> memory clearing? bootmem allocator or caller?

hm, bootmem allocator is supposed to clear memory. We have a couple of 
places that rely on that.

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