[Android 6.1] BUG: scheduling while atomic in wait_for_common

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 274e3e96961d ANDROID: export one function for mm metrics
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=13ff1cf4980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a340f281ebc7608
dashboard link: https://syzkaller.appspot.com/bug?extid=2e5fd55435a0d9acca62
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=16bf23b8980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=148c3378980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8be3794dd1a1/disk-274e3e96.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/614f8db9ab8d/vmlinux-274e3e96.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cfef4ed6662f/bzImage-274e3e96.xz

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

BUG: scheduling while atomic: syz-executor124/1926/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81b73417>] free_unref_page+0x177/0x5c0 mm/page_alloc.c:3621
CPU: 0 PID: 1926 Comm: syz-executor124 Not tainted 6.1.75-syzkaller-00009-g274e3e96961d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
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:5964
schedule_debug kernel/sched/core.c:5991 [inline]
__schedule+0xcf7/0x1550 kernel/sched/core.c:6626
schedule+0xc3/0x180 kernel/sched/core.c:6809
schedule_timeout+0xa9/0x380 kernel/time/timer.c:1917
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common+0x39a/0x640 kernel/sched/completion.c:117
wait_for_completion+0x18/0x20 kernel/sched/completion.c:138
kthread_stop+0x118/0x420 kernel/kthread.c:721
vhost_dev_cleanup+0x6f9/0x870 drivers/vhost/vhost.c:710
vhost_vsock_dev_release+0x3af/0x410 drivers/vhost/vsock.c:774
__fput+0x3ab/0x870 fs/file_table.c:320
____fput+0x15/0x20 fs/file_table.c:348
task_work_run+0x24d/0x2e0 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0x94/0xa0 kernel/entry/common.c:171
exit_to_user_mode_prepare+0x5a/0xa0 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x26/0x140 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fba761c34aa
Code: 48 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 53 84 02 00 8b 7c 24 0c 89 c2 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 d7 89 44 24 0c e8 b3 84 02 00 8b 44 24
RSP: 002b:00007ffd49fa2fb0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 000000000000000a RCX: 00007fba761c34aa
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000009
RBP: 00007ffd49fa3090 R08: 00007ffd49fe10b0 R09: 00007ffd49fa3120
R10: 00007ffd49fa3000 R11: 0000000000000293 R12: 00007fba76182e50
R13: 0000000000064413 R14: 0000000000064445 R15: 00007ffd49fa3020
</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