linux-kernel - Crypto Fixes for 4.1

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, 5 May 2015 18:06:21 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"David S. Miller" <davem@...emloft.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Crypto Mailing List <linux-crypto@...r.kernel.org>
Subject: Crypto Fixes for 4.1

Hi Linus:

This push fixes a build problem with bcm63xx and yet another fix
to the memzero_explicit function to ensure that the memset is not
elided.

Please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git

or

master.kernel.org:/pub/scm/linux/kernel/git/herbert/crypto-2.6.git


Daniel Borkmann (1):
      lib: make memzero_explicit more robust against dead store elimination

Álvaro Fernández Rojas (1):
      hwrng: bcm63xx - Fix driver compilation

 drivers/char/hw_random/bcm63xx-rng.c |   18 +++++++++---------
 include/linux/compiler-gcc.h         |   16 +++++++++++++++-
 include/linux/compiler-intel.h       |    3 +++
 include/linux/compiler.h             |    4 ++++
 lib/string.c                         |    2 +-
 5 files changed, 32 insertions(+), 11 deletions(-)

Thanks,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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/