On Wed, 16 Jul 2025 19:48:08 +0800, Ming Lei wrote:
> The lockdep tool can report a circular lock dependency warning in the loop
> driver's AIO read/write path:
>
> ```
> [ 6540.587728] kworker/u96:5/72779 is trying to acquire lock:
> [ 6540.593856] ff110001b5968440 (sb_writers#9){.+.+}-{0:0}, at: loop_process_work+0x11a/0xf70 [loop]
> [ 6540.603786]
> [ 6540.603786] but task is already holding lock:
> [ 6540.610291] ff110001b5968440 (sb_writers#9){.+.+}-{0:0}, at: loop_process_work+0x11a/0xf70 [loop]
> [ 6540.620210]
> [ 6540.620210] other info that might help us debug this:
> [ 6540.627499] Possible unsafe locking scenario:
> [ 6540.627499]
> [ 6540.634110] CPU0
> [ 6540.636841] ----
> [ 6540.639574] lock(sb_writers#9);
> [ 6540.643281] lock(sb_writers#9);
> [ 6540.646988]
> [ 6540.646988] *** DEADLOCK ***
> ```
>
> [...]
Applied, thanks!
[1/1] loop: use kiocb helpers to fix lockdep warning
commit: c4706c5058a7bd7d7c20f3b24a8f523ecad44e83
Best regards,
--
Jens Axboe
