Hi Kamil, On 2 February 2018 at 23:05, Kamil Konieczny <k.konieczny@xxxxxxxxxxxxxxxxxxx> wrote: > > > On 24.01.2018 15:01, Krzysztof Kozlowski wrote: >> On Wed, Jan 24, 2018 at 2:04 PM, Anand Moon <linux.amoon@xxxxxxxxx> wrote: >>> Hi Kamil Konieczny, >>> >>> I am looking in setup of encrypted sata hard-disk on Odroid XU4/HC1 device. >>> using following encryption method. >>> >>> aes-cbc-essiv:sha256 128 >>> aes-cbc-essiv:sha256 256 >>> >>> Here is my defconfig I am using. https://pastebin.com/gF5T2stp >>> >>> Following crypt benchmark we use to test : https://pastebin.com/WiexsJA2 >> >> No problems on my side with a 128 MB file (not a device): >> # cryptsetup -v luksFormat /tmp/testcrypt /dev/urandom >> --keyfile-size=32 --cipher aes-cbc-essiv:sha256 >> # Command successful. >> # cryptsetup -v luksFormat ~/testcrypt /dev/urandom --keyfile-size=32 >> --cipher aes-cbc-essiv:sha256 >> # Command successful. > > What version is cryptsetup ? > At my end I am using below version. root@odroid:~# cryptsetup --version cryptsetup 1.6.6 >> >> Linux 4.15.0-rc9-00023-g1f07476ec143. >> >> Some time ago you were building from not usual source code and your >> kernel version from WARN is not unambiguous. >> >> What is necessary to reproduce it? >>>[...] > > I get OOPS with cryptsetup 2.0.0, kernel 4.15 > I will try to get test with new version of cryptsetup 2.0.0. > If you have older cryptsetup, please keep it for reference. > > For now, I found that crypto-api or dm-crypt try to use aes-ecb > instead of aes-cbc, and sets req->info (pointer used for passing IV) to 0x10 > Ok. Best Regards -Anand > -- > Best regards, > Kamil Konieczny > Samsung R&D Institute Poland >
