[Android 5.15] BUG: scheduling while atomic in unlink_anon_vmas

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ad06eaf051cd Merge branch 'android13-5.15' into branch 'an..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=11318abb180000
kernel config: https://syzkaller.appspot.com/x/.config?x=49ce29477ba81e8f
dashboard link: https://syzkaller.appspot.com/bug?extid=7b06b4653d350d63d705
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=15a7a99f180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1395f107180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/11af0aa6a668/disk-ad06eaf0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4402d93fba04/vmlinux-ad06eaf0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f6d6b2b05230/bzImage-ad06eaf0.xz

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

BUG: scheduling while atomic: syz-executor425/316/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8165eb4a>] is_module_text_address+0x1a/0x140 kernel/module.c:4811
CPU: 1 PID: 316 Comm: syz-executor425 Not tainted 5.15.148-syzkaller-00013-gad06eaf051cd #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/0x17 lib/dump_stack.c:113
__schedule_bug+0x195/0x260 kernel/sched/core.c:5707
schedule_debug kernel/sched/core.c:5734 [inline]
__schedule+0xd19/0x1590 kernel/sched/core.c:6402
schedule+0x11f/0x1e0 kernel/sched/core.c:6595
rwsem_down_write_slowpath+0xde4/0x1d70 kernel/locking/rwsem.c:1207
__down_write_common kernel/locking/rwsem.c:1341 [inline]
__down_write kernel/locking/rwsem.c:1350 [inline]
down_write+0x29/0x30 kernel/locking/rwsem.c:1603
lock_anon_vma_root mm/rmap.c:250 [inline]
unlink_anon_vmas+0xf0/0x590 mm/rmap.c:407
free_pgtables+0x137/0x280 mm/memory.c:485
exit_mmap+0x3e7/0x6f0 mm/mmap.c:3210
__mmput+0x95/0x310 kernel/fork.c:1179
mmput+0x5b/0x170 kernel/fork.c:1202
exit_mm kernel/exit.c:552 [inline]
do_exit+0xb9c/0x2ca0 kernel/exit.c:865
do_group_exit+0x141/0x310 kernel/exit.c:1000
__do_sys_exit_group kernel/exit.c:1011 [inline]
__se_sys_exit_group kernel/exit.c:1009 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1009
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f2554f57039
Code: Unable to access opcode bytes at RIP 0x7f2554f5700f.
RSP: 002b:00007ffc51646588 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f2554f57039
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007f2554fd32b0 R08: ffffffffffffffb8 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f2554fd32b0
R13: 0000000000000000 R14: 00007f2554fd3d20 R15: 00007f2554f281d0
</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