commit f9e2bca6c22d75a289a349f869701214d63b5060
aka crypto: sha512 - Move message schedule W[80] to static percpu area
created global message schedule area.
If sha512_update will ever be entered twice, hash will be silently
calculated incorrectly.
Probably the easiest way to notice incorrect
Le samedi 14 janvier 2012 à 21:27 +0300, Alexey Dobriyan a écrit :
commit f9e2bca6c22d75a289a349f869701214d63b5060
aka crypto: sha512 - Move message schedule W[80] to static percpu area
created global message schedule area.
Signed-off-by: Alexey Dobriyan adobri...@gmail.com
Cc:
On Sat, Jan 14, 2012 at 1:46 PM, Eric Dumazet eric.duma...@gmail.com wrote:
This is too risky, and we provided an alternate patch, not just for fun.
Did you see the second patch?
The one that got rid of the *stupid* 80-entry array?
I don't know why so many sha implementations do that idiotic
Le samedi 14 janvier 2012 à 13:52 -0800, Linus Torvalds a écrit :
On Sat, Jan 14, 2012 at 1:46 PM, Eric Dumazet eric.duma...@gmail.com wrote:
This is too risky, and we provided an alternate patch, not just for fun.
Did you see the second patch?
I saw it and felt it was not a stable
On Sat, Jan 14, 2012 at 09:27:37PM +0300, Alexey Dobriyan wrote:
commit f9e2bca6c22d75a289a349f869701214d63b5060
aka crypto: sha512 - Move message schedule W[80] to static percpu area
created global message schedule area.
If sha512_update will ever be entered twice, hash will be silently