On Tue, Mar 01, 2016 at 01:32:05AM +0000, Eric Wheeler wrote: > Hello all, > > We updated from 4.1.17 to 4.1.18 (same .config) and now get the following > error when trying to open a LUKS volume. We've reverted to 4.1.17 and it > still works, so except that I'm not sure which commit caused the problem, > it is likely one of the recent commits: > > When we `cryptsetup luksOpen` the volume we get this: > > Check that kernel supports aes-cbc-essiv:sha256 cipher (check syslog for more info). > > Note that I do not see any dm-crypto commits so I don't think its a > dm-crypto issue. > > I'm happy to test, but can someone who knows the crypto stack suggest > which of these patches I should focus on for testing? These are the > commits in 4.1.18 that could be relevant: There are some pending crypto backports to resolve this that hopefully will show up in the next release, whenever Sasha gets to it. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html