[PATCH] MPI: Endianness fix

The limbs are integers in the host endianness, so we can't simply iterate over the individual bytes. The current code happens to work on little-endian, because the order of the limbs in the MPI array is the same as the order of the bytes in each limb, but it breaks on big-endian. Fixes:

Broken userspace crypto in linux-4.1.18

Hi, something is broken with crypto in linux-4.1.18. On my system I have two disks (sda and sdb), both encrypted with LUKS (cipher=aes-xts-plain64). My rootfs resides encrypted on sda2 (sda1 is an unencrypted boot partition). sdb has one full encrypted partition (sdb1) mounted in "/backup".

Re: Broken userspace crypto in linux-4.1.18

On 02/17/2016 09:04 AM, Thomas D. wrote: > Hi, > > something is broken with crypto in linux-4.1.18. > > On my system I have two disks (sda and sdb), both encrypted with LUKS > (cipher=aes-xts-plain64). > > My rootfs resides encrypted on sda2 (sda1 is an unencrypted boot > partition). > sdb has

Re: Broken userspace crypto in linux-4.1.18

Hi, Sasha Levin wrote: > So either the upstream patch is broken, or the 4.1 backport is wrong/missing > dependency/missing fix. > > Any chance you could try 4.5-rc3 and see if that works for you? That'll narrow > it down a lot. 4.5-rc3 works for me. Linux-4.4.0 works, too. -Thomas -- To

Re: Broken userspace crypto in linux-4.1.18

On 02/17/2016 10:24 AM, Thomas D. wrote: > Hi, > > Sasha Levin wrote: >> > So either the upstream patch is broken, or the 4.1 backport is >> > wrong/missing >> > dependency/missing fix. >> > >> > Any chance you could try 4.5-rc3 and see if that works for you? That'll >> > narrow >> > it down a

Re: Broken userspace crypto in linux-4.1.18

On Wed, Feb 17, 2016 at 05:12:56PM -0500, Sasha Levin wrote: > On 02/17/2016 10:24 AM, Thomas D. wrote: > > Hi, > > > > Sasha Levin wrote: > >> > So either the upstream patch is broken, or the 4.1 backport is > >> > wrong/missing > >> > dependency/missing fix. > >> > > >> > Any chance you could

Re: Broken userspace crypto in linux-4.1.18

Hi Willy Tarreau wrote: >> Is there a dependency I missed in 4.1? I don't really see anything that >> could have gone wrong there. > > Or maybe Thomas can run a bisect ? I cannot follow. I did a bisect between 4.1.7 and 4.1.8 as I have written in my first mail. The bad commit was: > commit

Re: Broken userspace crypto in linux-4.1.18

On Thu, Feb 18, 2016 at 12:49:57AM +0100, Thomas D. wrote: > Hi > > Willy Tarreau wrote: > >> Is there a dependency I missed in 4.1? I don't really see anything that > >> could have gone wrong there. > > > > Or maybe Thomas can run a bisect ? > > I cannot follow. I did a bisect between 4.1.7

Re: [PATCH] vti6: Add pmtu handling to vti6_xmit.

On 17/02/16 20:08, Steffen Klassert wrote: > On Wed, Feb 10, 2016 at 01:50:20AM +, Mark McKinstry wrote: >>> So this version is slightly modified to cover the IPv4 case in addition to >>> the IPv6 case. With this patch I was able to run netperf over either an >>> IPv4 or IPv6 address routed

[PATCH] The AE id should be less than the maximal AE number

Signed-off-by: Yang Pingchao --- drivers/crypto/qat/qat_common/qat_uclo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/crypto/qat/qat_common/qat_uclo.c b/drivers/crypto/qat/qat_common/qat_uclo.c index 25d15f1..9b961b3 100644 ---

[cryptodev:master 95/102] arch/arm64/crypto/aes-glue.c:88:2: error: implicit declaration of function 'xts_check_key'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master head: 49abc0d2e19b28e90f443334fb6cd66f275713e6 commit: 28856a9e52c7cac712af6c143de04766617535dc [95/102] crypto: xts - consolidate sanity check for keys config: arm64-defconfig (attached as .config)