dm verity: fix no salt use case
authorGilad Ben-Yossef <gilad@benyossef.com>
Thu, 18 May 2017 10:47:25 +0000 (13:47 +0300)
committerMike Snitzer <snitzer@redhat.com>
Mon, 22 May 2017 17:49:03 +0000 (13:49 -0400)
commitf52236e0b0a0820e938e16a776309e76b7bd6c43
treeca0094e3a1a789be5f5346c79884927e5e43e264
parent08332893e37af6ae779367e78e444f8f9571511d
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>
drivers/md/dm-verity-target.c