Re: [bug report] WARNING: CPU: 12 PID: 51497 at block/mq-deadline.c:679 dd_exit_sched+0xd5/0xe0

Changhui Zhong
2023-08-21T02:18:44Z

On Mon, Aug 21, 2023 at 9:56 AM Jens Axboe <axboe@kernel.dk> wrote:
>
> On 8/20/23 7:43 PM, Changhui Zhong wrote:
> > Hello,
> >
> > triggered below warning issue with branch 'block-6.5',
>
> What sha? Please always include that in bug reports, people don't know
> when you pulled it.
>

ok,I pulled the whole branch of block-6.5, I don't know which patch
caused the issue，the HEAD is：
"
INFO: HEAD of cloned kernel
/mnt/tests/kernel/distribution/upstream-kernel/install/kernel
/mnt/tests/kernel/distribution/upstream-kernel/install
/mnt/tests/kernel/distribution/upstream-kernel/install
commit cc7de17e2fe6b778a836032e7e5f9991dec40a25
Author: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Date: Thu Aug 17 10:15:56 2023 -0400

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>
"