linux-kernel - Re: [uClinux-dev] [PATCH] NOMMU: fix malloc performance by addinguninitialized flag

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]

Date:	Tue, 13 Oct 2009 11:20:59 -0400
From:	Robin Getz <rgetz@...ckfin.uclinux.org>
To:	"Mike Frysinger" <vapier@...too.org>
CC:	uclinux-dev@...inux.org, "David Howells" <dhowells@...hat.com>,
	"David McCullough" <davidm@...pgear.com>,
	"Greg Ungerer" <gerg@...inux.org>,
	"Paul Mundt" <lethal@...ux-sh.org>,
	uclinux-dist-devel@...ckfin.uclinux.org,
	linux-kernel@...r.kernel.org, "Zhang, Jie" <jie.zhang@...log.com>
Subject: Re: [uClinux-dev] [PATCH] NOMMU: fix malloc performance by addinguninitialized flag

On Tue 13 Oct 2009 03:44, Mike Frysinger pondered:
> From: Jie Zhang <jie.zhang@...log.com>
> 
> The no-mmu code currently clears all anonymous mmap-ed memory.  While this
> is what we want in the default case, all memory allocation from userspace
> under no-mmu has to go through this interface, including malloc() which is
> allowed to return uninitialized memory.  This can easily be a significant
> performance slow down.  So for constrained embedded systems were security
> is irrelevant, allow people to avoid unnecessarily clearing memory.
> 
> Signed-off-by: Jie Zhang <jie.zhang@...log.com>
> Signed-off-by: Robin Getz <rgetz@...log.com>

Should be rgetz@...ckfin.uclinux.org -- rgetz@...log.com does not exist and will bounce.

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