Re: luks container created on a system won't luksOpen on another

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



hi Milan,

On Thu, Sep 10, 2015 at 04:14:39PM +0200, Milan Broz wrote:
[...]
> This could be the problem I guess:
> 
> > name         : __xts-aes-neonbs
> ...
> 
> So it is using NEON acceleration on ARM.
> 
> There was a bug in NEON kernel implementation, see
> http://www.saout.de/pipermail/dm-crypt/2015-February/004632.html
> 
> Could you read that thread and try workaround I mentioned there?
> http://www.saout.de/pipermail/dm-crypt/2015-February/004631.html

spot on...

the kernel i was using has all the crypto ciphers compiled in so i
couldn't unload the aes_arm_bs cipher, but looking at your other
message (re patch for the kernel bug) i installed a newer kernel that
includes the NEON patch and this works perfectly, thank you!

best
andrea

Attachment: signature.asc
Description: Digital signature

_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt

[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux