From: 23pieces <23pieces@protonmail.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: dm-crypt patch in Linux 4.20.6 Commit e4efd3184d9a63a7923e5c62fa236254f03c6bf8
Date: Fri, 08 Feb 2019 11:39:00 +0000 [thread overview]
Message-ID: <1uWvFLIArHW8L5PlgMMbXz1fok_GsLiCTltivAZWDl9rHLjihpxmIzakchb_s1Ad_S267Ia3FqRj-fgsrm-ROZZuGVBOlHB1lplVZswHzNE=@protonmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1886 bytes --]
Hello everyone!
It seems since kernelversion 4.20.6 many people have problems mounting their encrypted rootfs while booting.
Trying to investigate i found this commit in 4.20.6:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/md/dm-crypt.c?id=e4efd3184d9a63a7923e5c62fa236254f03c6bf8
To clarify this issue also persists in 4.20.7 and isn't occuring in 4.20.5.
People having the problem often have something like the following config on their rootfs (including myself):
cryptsetup -v --type luks --cipher aes-xts-plain64 --key-size 512 --hash sha512 --iter-time 5000 --use-random --verify-passphrase luksFormat device
I was trying to investigate the code in the commit and playing around with the dmsetup commands mentioned.
Now on a running system with kernel 4.20.6 i get:
dmsetup create test --table "0 8 crypt aes-cbc-essiv:sha3-256 9c1185a5c5e9fc54612808977ee8f5b9e 0 /dev/sdc 0" Works
dmsetup create test --table "0 8 crypt aes-cbc-essiv:sha512 9c1185a5c5e9fc54612808977ee8f5b9e 0 /dev/sdc 0"
device-mapper: reload ioctl on test failed: Invalid argument
Command failed.
dmsetup create test --table "0 8 crypt aes-xts-plain-64:sha3-256 9c1185a5c5e9fc54612808977ee8f5b9e 0 /dev/sdc 0"
device-mapper: reload ioctl on test failed: Invalid argument
Command failed.
dmsetup create test --table "0 8 crypt aes-xts-plain-64:sha512 9c1185a5c5e9fc54612808977ee8f5b9e 0 /dev/sdc 0"
device-mapper: reload ioctl on test failed: Invalid argument
Command failed.
At boot people have the following error:
device-mapper: reload ioctl on failed: Invalid argument
Failed to setup dm-crypt key mapping for device /dev/disk/by-uuid/UUID
Check that kernel supports aes-xts-plain-64 cipher (check syslog for more info)
I don't have a patch for this yet, just wanted to inform you.
Best regards
23pieces
[-- Attachment #1.2: publickey - 23pieces@protonmail.com - 0xC6F1867B.asc --]
[-- Type: application/pgp-keys, Size: 1823 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]
next reply other threads:[~2019-02-08 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 11:39 23pieces [this message]
2019-02-08 11:58 ` dm-crypt patch in Linux 4.20.6 Commit e4efd3184d9a63a7923e5c62fa236254f03c6bf8 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='1uWvFLIArHW8L5PlgMMbXz1fok_GsLiCTltivAZWDl9rHLjihpxmIzakchb_s1Ad_S267Ia3FqRj-fgsrm-ROZZuGVBOlHB1lplVZswHzNE=@protonmail.com' \
--to=23pieces@protonmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).