[PATCH 3.10 101/180] crypto: ux500 - memmove the right size

2016-08-21 Thread Willy Tarreau
From: Linus Walleij commit 19ced623db2fe91604d69f7d86b03144c5107739 upstream. The hash buffer is really HASH_BLOCK_SIZE bytes, someone must have thought that memmove takes n*u32 words by mistake. Tests work as good/bad as before after this patch. Cc: Joakim Bech Cc: sta...@vger.kernel.org Repo

[PATCH 3.16 183/305] crypto: ux500 - memmove the right size

2016-08-14 Thread Ben Hutchings
3.16.37-rc1 review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 19ced623db2fe91604d69f7d86b03144c5107739 upstream. The hash buffer is really HASH_BLOCK_SIZE bytes, someone must have thought that memmove takes n*u32 words by mistake. Te

[PATCH 3.14 01/53] crypto: ux500 - memmove the right size

2016-07-25 Thread Greg Kroah-Hartman
3.14-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 19ced623db2fe91604d69f7d86b03144c5107739 upstream. The hash buffer is really HASH_BLOCK_SIZE bytes, someone must have thought that memmove takes n*u32 words by mistake. Te

[PATCH 3.12 45/88] crypto: ux500 - memmove the right size

2016-07-14 Thread Jiri Slaby
From: Linus Walleij 3.12-stable review patch. If anyone has any objections, please let me know. === commit 19ced623db2fe91604d69f7d86b03144c5107739 upstream. The hash buffer is really HASH_BLOCK_SIZE bytes, someone must have thought that memmove takes n*u32 words by mistake. Tests

Re: crypto: ux500 - memmove the right size

2016-07-11 Thread Herbert Xu
On Mon, Jul 11, 2016 at 04:40:34PM +0200, Toralf Förster wrote: > While reading the comment to 19ced623d : > > "The hash buffer is really HASH_BLOCK_SIZE bytes, someone > must have thought that memmove takes n*u32 words by mistake. > Tests work as good/bad as before after this patch. >

Re: crypto: ux500 - memmove the right size

2016-07-11 Thread Toralf Förster
While reading the comment to 19ced623d : "The hash buffer is really HASH_BLOCK_SIZE bytes, someone must have thought that memmove takes n*u32 words by mistake. Tests work as good/bad as before after this patch. " I was just curious why the tests doesn't fail now and since when the bug

[PATCH 4.6 15/31] crypto: ux500 - memmove the right size

2016-07-06 Thread Greg Kroah-Hartman
4.6-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 19ced623db2fe91604d69f7d86b03144c5107739 upstream. The hash buffer is really HASH_BLOCK_SIZE bytes, someone must have thought that memmove takes n*u32 words by mistake. Tes

[PATCH 4.4 16/32] crypto: ux500 - memmove the right size

2016-07-06 Thread Greg Kroah-Hartman
4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 19ced623db2fe91604d69f7d86b03144c5107739 upstream. The hash buffer is really HASH_BLOCK_SIZE bytes, someone must have thought that memmove takes n*u32 words by mistake. Tes