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>
Mon, 16 Sep 2019 06:22:14 +0000 (08:22 +0200)
commitfcb2f1e2ea687b3507b11c8e74c30dd3d967f1b0
tree6e9280f3af984ee11fe18b2f599eabcdb4469257
parent96b44c20e6f0694b41c690da4ecfe9a1297879d2
dm crypt: move detailed message into debug level

[ Upstream commit 7a1cd7238fde6ab367384a4a2998cba48330c398 ]

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: Sasha Levin <sashal@kernel.org>
drivers/md/dm-crypt.c