Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Nicolas Porcel <nicolasporcel06@gmail.com>
To: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Subject: crypto: xts: regression in 4.10
Date: Wed, 22 Feb 2017 00:17:17 +0100	[thread overview]
Message-ID: <20170221231717.GA7186@nicolas-laptop> (raw)

Hello,

I am using aes-xts-plain64 with LUKS headers to crypt the root. In 4.10,
the partition cannot be opened and I have the following errors when
booting:

    device-mapper: table: 253:0: crypt: Error allocating crypto tfm
    device-mapper: ioctl: error adding target to table
    device-mapper: reload ioctl on  failed: No such file or directory
    Failed to setup dm-crypt key mapping for device /dev/mmcblk0p2
    Check that the kernel supports aes-xts-plain64 cipher (check syslog for more info)

I found that this commit is responsible for the regression (reverting it
solves the problem):

> commit f1c131b45410a202eb45cc55980a7a9e4e4b4f40
> Author: Herbert Xu <herbert@gondor.apana.org.au>
> Date:   Tue Nov 22 20:08:19 2016 +0800
> 
>     crypto: xts - Convert to skcipher

Some precision: I am using the vanilla kernel source for 4.10. The aes,
xts and dm-crypt modules are directly compiled in the kernel and not as
modules. I also had the same problem with kernel 4.10-rc*.

Is it a known issue? I found 1 related email with no answer on the
dm-crypt mailing. If this is a regression, I can start digging, although
any guidance would be greatly appreciated.

Thank you in advance,

Best regards,

-- 
Nicolas Porcel

             reply	other threads:[~2017-02-21 23:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 23:17 Nicolas Porcel [this message]
2017-02-22 11:31 ` crypto: xts: regression in 4.10 Milan Broz
2017-02-22 23:02   ` Nicolas Porcel
2017-02-22 17:42 ` Marcelo Cerri
2017-02-23  7:38 ` [PATCH] crypto: Add ECB dependency for XTS mode Milan Broz
2017-02-23 12:17   ` Herbert Xu
2017-03-03  6:25   ` Milan Broz
2017-03-10  7:36     ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170221231717.GA7186@nicolas-laptop \
    --to=nicolasporcel06@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox