Hi Ted,
On 09/15/2014 01:52 PM, Herbert Xu wrote:
On Sun, Sep 07, 2014 at 11:23:38PM +0200, Daniel Borkmann wrote:
Recently, in commit 13aa93c70e71 (random: add and use memzero_explicit()
for clearing data), we have found that GCC may optimize some memset()
cases away when it detects a stack
On Sun, Sep 07, 2014 at 11:23:38PM +0200, Daniel Borkmann wrote:
Recently, in commit 13aa93c70e71 (random: add and use memzero_explicit()
for clearing data), we have found that GCC may optimize some memset()
cases away when it detects a stack variable is not being used anymore
and going out of
On So, 2014-09-07 at 23:23 +0200, Daniel Borkmann wrote:
Recently, in commit 13aa93c70e71 (random: add and use memzero_explicit()
for clearing data), we have found that GCC may optimize some memset()
cases away when it detects a stack variable is not being used anymore
and going out of scope.
On Mon, 8 Sep 2014, Hannes Frederic Sowa wrote:
On So, 2014-09-07 at 23:23 +0200, Daniel Borkmann wrote:
Recently, in commit 13aa93c70e71 (random: add and use memzero_explicit()
for clearing data), we have found that GCC may optimize some memset()
cases away when it detects a stack
