Hi Yureka, On Fri, Sep 29, 2023 at 11:08:55PM +0200, Yureka wrote: > #regzbot introduced: 7bcb2c99f8ed > > I am running the NixOS distribution cross-compiled from x86_64 to a Marvell > Armada 388 armv7 SoC. > > I am not getting expected speeds when reading/writing on my encrypted hard > drive with 6.5.5, while it is fast on 5.4.257. Volume is formatted like this: > `cryptsetup luksFormat -c aes-cbc-essiv:sha256 /dev/sda`. > > Specifically, I tracked this down to the changes to crypto/essiv.c from > 7bcb2c99f8ed mentioned above. Reverting those changes on top of a 6.5.5 kernel > provides working (see applicable diff further below). > > I'm *guessing* that this is related to the mv-aes-cbc crypto driver (from the > marvell-cesa module) being registered as async (according to /proc/crypto), > and I *suspect* that async drivers are not being used anymore by essiv or > dm_crypt. Going by the commit description, which sounds more like a refactor, > this does not seem intentional. This is actually from commit b8aa7dc5c753 ("crypto: drivers - set the flag CRYPTO_ALG_ALLOCATES_MEMORY"), which set CRYPTO_ALG_ALLOCATES_MEMORY in marvell-cesa. 7bcb2c99f8ed is just one of the prerequisite commits. I understand that the dm-crypt developers did this as an intentional bug fix in order to prevent dm-crypt from using crypto drivers that are known to cause deadlocks due to allocating memory during requests. If you are interested in still being able to use marvell-cesa with dm-crypt, I believe it would need to be fixed to meet the requirements for not needing CRYPTO_ALG_ALLOCATES_MEMORY. I've Cc'ed the maintainers of that driver. #regzbot introduced: b8aa7dc5c753 - Eric