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  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]
Date:	Tue, 26 Jun 2007 20:45:28 -0700
From:	"Ulrich Drepper" <>
To:	"Rik van Riel" <>
Cc:	"Davide Libenzi" <>,
	"Linux Kernel Mailing List" <>
Subject: Re: [patch 2/3] MAP_NOZERO - implement sys_brk2()

On 6/26/07, Rik van Riel <> wrote:
> Since programs can get back free()d memory after a malloc(),
> with the old contents of the memory intact, surely your
> MAP_NONZERO behavior could be the default for programs that
> can get away with it?
> Maybe we could use some magic ELF header, similar to the
> way non-executable stack is handled?

No.  This is an implementation detail of the libc version.  The malloc
as compiled today is expecting brk-ed memory to be zeroed.  This
default can of course be changed (it's a simple define) but you cannot
make this the default behavior for brk.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists