[dm-crypt] luks container created on a system won't luksOpen on another

andrea rota a at xelera.eu
Thu Sep 10 17:19:41 CEST 2015

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!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1513 bytes
Desc: Digital signature
URL: <http://www.saout.de/pipermail/dm-crypt/attachments/20150910/f18e796b/attachment.asc>

More information about the dm-crypt mailing list