dm crypt: move detailed message into debug level
authorMilan Broz <gmazyland@gmail.com>
Wed, 15 May 2019 14:23:43 +0000 (16:23 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 25 May 2019 16:22:19 +0000 (18:22 +0200)
commitecff1441aa15571b1297dfb4ac16812223112802
tree2759f6fe6073b40b56b62e731991bd8971944c73
parent862a78341ade4fa52da2803e48e8c271b7fbf6e8
dm crypt: move detailed message into debug level

commit 7a1cd7238fde6ab367384a4a2998cba48330c398 upstream.

The information about tag size should not be printed without debug info
set. Also print device major:minor in the error message to identify the
device instance.

Also use rate limiting and debug level for info about used crypto API
implementaton.  This is important because during online reencryption
the existing message saturates syslog (because we are moving hotzone
across the whole device).

Cc: stable@vger.kernel.org
Signed-off-by: Milan Broz <gmazyland@gmail.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/md/dm-crypt.c