[Android 6.1] BUG: scheduling while atomic in unlink_anon_vmas

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b75112544779 ANDROID: Add symbols for IIO SCMI module
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=144c3231180000
kernel config: https://syzkaller.appspot.com/x/.config?x=54c503ca94c7e582
dashboard link: https://syzkaller.appspot.com/bug?extid=a65f9b622c7c6ff70866
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=125abffa180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16309d66180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/39510a2dc9da/disk-b7511254.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3e59d46d8461/vmlinux-b7511254.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8e0de5e3bcaa/bzImage-b7511254.xz

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

BUG: scheduling while atomic: syz-executor423/649/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8163ef8f>] is_module_text_address+0x1f/0x360 kernel/module/main.c:3140
CPU: 1 PID: 649 Comm: syz-executor423 Not tainted 6.1.68-syzkaller-00089-gb75112544779 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/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:5960
schedule_debug kernel/sched/core.c:5987 [inline]
__schedule+0xcf7/0x1550 kernel/sched/core.c:6622
schedule+0xc3/0x180 kernel/sched/core.c:6805
rwsem_down_write_slowpath+0xddf/0x20a0 kernel/locking/rwsem.c:1227
__down_write_common kernel/locking/rwsem.c:1357 [inline]
__down_write kernel/locking/rwsem.c:1366 [inline]
down_write+0x21/0x30 kernel/locking/rwsem.c:1619
lock_anon_vma_root mm/rmap.c:253 [inline]
unlink_anon_vmas+0xf0/0x5b0 mm/rmap.c:410
free_pgtables+0x4af/0x660 mm/memory.c:441
exit_mmap+0x415/0x940 mm/mmap.c:3341
__mmput+0x95/0x310 kernel/fork.c:1298
mmput+0x56/0x170 kernel/fork.c:1321
exit_mm kernel/exit.c:566 [inline]
do_exit+0xb29/0x2b80 kernel/exit.c:862
do_group_exit+0x21a/0x2d0 kernel/exit.c:1025
__do_sys_exit_group kernel/exit.c:1036 [inline]
__se_sys_exit_group kernel/exit.c:1034 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1034
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f739fc88039
Code: Unable to access opcode bytes at 0x7f739fc8800f.
RSP: 002b:00007ffdcb2f3788 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f739fc88039
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007f739fd042b0 R08: ffffffffffffffb8 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f739fd042b0
R13: 0000000000000000 R14: 00007f739fd04d20 R15: 00007f739fc591c0
</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