On Fri, 09 Jun 2023 23:11:39 -0700, Eric Biggers wrote:
> When a device-mapper device is passing through the inline encryption
> support of an underlying device, calls to blk_crypto_evict_key() take
> the blk_crypto_profile::lock of the device-mapper device, then take the
> blk_crypto_profile::lock of the underlying device (nested). This isn't
> a real deadlock, but it causes a lockdep report because there is only
> one lock class for all instances of this lock.
>
> [...]
Applied, thanks!
[1/1] blk-crypto: use dynamic lock class for blk_crypto_profile::lock
commit: de9f927faf8dfb158763898e09a3e371f2ebd30d
Best regards,
--
Jens Axboe
