[Android 6.1] BUG: workqueue leaked lock or atomic in free_work

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d3f73f04529a UPSTREAM: drm/msm/dsi: Use pm_runtime_resume_..
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=157f9242180000
kernel config: https://syzkaller.appspot.com/x/.config?x=54c503ca94c7e582
dashboard link: https://syzkaller.appspot.com/bug?extid=7a03a760f641ac52987b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1623a498180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1362eaec180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b8ac49530c97/disk-d3f73f04.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c62ae40664b6/vmlinux-d3f73f04.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f84dcf9b0a66/bzImage-d3f73f04.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7a03a7...@syzkaller.appspotmail.com

BUG: workqueue leaked lock or atomic: kworker/1:2/0x00000001/824
last function: free_work
CPU: 1 PID: 824 Comm: kworker/1:2 Not tainted 6.1.68-syzkaller-00008-gd3f73f04529a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: events free_work
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x1b lib/dump_stack.c:113
process_one_work+0x94e/0xcb0 kernel/workqueue.c:2314
worker_thread+0xa60/0x1260 kernel/workqueue.c:2446
kthread+0x26d/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
BUG: scheduling while atomic: kworker/1:2/824/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81b65ac6>] spin_lock include/linux/spinlock.h:350 [inline]
[<ffffffff81b65ac6>] free_vmap_area_noflush+0x226/0xa30 mm/vmalloc.c:1837
CPU: 1 PID: 824 Comm: kworker/1:2 Not tainted 6.1.68-syzkaller-00008-gd3f73f04529a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: 0x0 (events)
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x1b lib/dump_stack.c:113
__schedule_bug+0x195/0x260 kernel/sched/core.c:5960
schedule_debug kernel/sched/core.c:5987 [inline]
__schedule+0xce9/0x1540 kernel/sched/core.c:6622
schedule+0xc3/0x180 kernel/sched/core.c:6805
worker_thread+0xefa/0x1260 kernel/workqueue.c:2467
kthread+0x26d/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup