blk-crypto: dynamically allocate fallback profile
authorSweet Tea Dorminy <sweettea-kernel@dorminy.me>
Thu, 17 Aug 2023 14:15:56 +0000 (10:15 -0400)
committerJens Axboe <axboe@kernel.dk>
Fri, 18 Aug 2023 21:00:39 +0000 (15:00 -0600)
commitc984ff1423ae9f70b1f28ce811856db0d9c99021
tree4951e9214ede8f9b1fba254c2daca9a4b8948544
parentc164c7bc9775be7bcc68754bb3431fce5823822e
blk-crypto: dynamically allocate fallback profile

blk_crypto_profile_init() calls lockdep_register_key(), which warns and
does not register if the provided memory is a static object.
blk-crypto-fallback currently has a static blk_crypto_profile and calls
blk_crypto_profile_init() thereupon, resulting in the warning and
failure to register.

Fortunately it is simple enough to use a dynamically allocated profile
and make lockdep function correctly.

Fixes: 2fb48d88e77f ("blk-crypto: use dynamic lock class for blk_crypto_profile::lock")
Cc: stable@vger.kernel.org
Signed-off-by: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Reviewed-by: Eric Biggers <ebiggers@google.com>
Link: https://lore.kernel.org/r/20230817141615.15387-1-sweettea-kernel@dorminy.me
Signed-off-by: Jens Axboe <axboe@kernel.dk>
block/blk-crypto-fallback.c