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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <aa79d98a0804072250l304232e3h29d08febb812b5f9@mail.gmail.com>
Date:	Tue, 8 Apr 2008 09:50:50 +0400
From:	"Cyrill Gorcunov" <gorcunov@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Yinghai Lu" <yhlu.kernel@...il.com>,
	"Andi Kleen" <andi@...stfloor.org>, "Ingo Molnar" <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: bootmem allocator

On Tue, Apr 8, 2008 at 8:33 AM, H. Peter Anvin <hpa@...or.com> wrote:
> Cyrill Gorcunov wrote:
>
> >
> > I think it would be a good idea ;) Btw maybe would be better to call
> > memset on the code witch relies on "clear" memory explicitly? So we will
> > clear memory allocated *only* if we really need this.
>
>  Are there any users of bootmem which will allocate a significant amount of
> memory and don't need it zeroed?
>
>         -hpa
>

Actually, I don't know without reading the code... will take a look
today evening
(have no access to sources in my office).
--
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/