dm integrity: fail early if required HMAC key is not available
authorMilan Broz <gmazyland@gmail.com>
Tue, 13 Feb 2018 13:50:50 +0000 (14:50 +0100)
committerMike Snitzer <snitzer@redhat.com>
Tue, 3 Apr 2018 19:04:16 +0000 (15:04 -0400)
commite16b4f99f0f79682a7efe191a8ce694d87ca9fc8
tree8176b07c744f1d532d629cb9a5b20159f16357cd
parent2d77dafe23b6c0cc9e501bda0e3f138b96ecd811
dm integrity: fail early if required HMAC key is not available

Since crypto API commit 9fa68f62004 ("crypto: hash - prevent using keyed
hashes without setting key") dm-integrity cannot use keyed algorithms
without the key being set.

The dm-integrity recognizes this too late (during use of HMAC), so it
allows creation and formatting of superblock, but the device is in fact
unusable.

Fix it by detecting the key requirement in integrity table constructor.

Signed-off-by: Milan Broz <gmazyland@gmail.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
drivers/md/dm-integrity.c