aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/md/dm-integrity.c
diff options
context:
space:
mode:
authorGilad Ben-Yossef <gilad@benyossef.com>2017-05-18 13:47:25 +0300
committerMike Snitzer <snitzer@redhat.com>2017-05-22 13:49:03 -0400
commitf52236e0b0a0820e938e16a776309e76b7bd6c43 (patch)
treeca0094e3a1a789be5f5346c79884927e5e43e264 /drivers/md/dm-integrity.c
parentLinux 4.12-rc2 (diff)
downloadlinux-dev-f52236e0b0a0820e938e16a776309e76b7bd6c43.tar.xz
linux-dev-f52236e0b0a0820e938e16a776309e76b7bd6c43.zip
dm verity: fix no salt use case
DM-Verity has an (undocumented) mode where no salt is used. This was never handled directly by the DM-Verity code, instead working due to the fact that calling crypto_shash_update() with a zero length data is an implicit noop. This is no longer the case now that we have switched to crypto_ahash_update(). Fix the issue by introducing explicit handling of the no salt use case to DM-Verity. Signed-off-by: Gilad Ben-Yossef <gilad@benyossef.com> Reported-by: Marian Csontos <mcsontos@redhat.com> Fixes: d1ac3ff ("dm verity: switch to using asynchronous hash crypto API") Tested-by: Milan Broz <gmazyland@gmail.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'drivers/md/dm-integrity.c')
0 files changed, 0 insertions, 0 deletions