[v6.1] BUG: sleeping function called from invalid context in exit_mmap

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f1bb70486c9c Linux 6.1.77
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10c76de0180000
kernel config: https://syzkaller.appspot.com/x/.config?x=39447811cb133e7e
dashboard link: https://syzkaller.appspot.com/bug?extid=d4537ef54c2cacf80745
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=1739e3a2180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d17520180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b4e70e158586/disk-f1bb7048.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6fd889f445ac/vmlinux-f1bb7048.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3c8bf6d15492/bzImage-f1bb7048.xz

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

BUG: sleeping function called from invalid context at mm/mmap.c:3251
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 6766, name: syz-executor151
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
1 lock held by syz-executor151/6766:
#0: ffff88807d4d6a58 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock include/linux/mmap_lock.h:71 [inline]
#0: ffff88807d4d6a58 (&mm->mmap_lock){++++}-{3:3}, at: exit_mmap+0x29a/0x9f0 mm/mmap.c:3235
Preemption disabled at:
[<ffffffff817677fa>] is_module_text_address+0x1a/0x160 kernel/module/main.c:3097
CPU: 0 PID: 6766 Comm: syz-executor151 Not tainted 6.1.77-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
__might_resched+0x5cb/0x780 kernel/sched/core.c:9942
exit_mmap+0x54b/0x9f0 mm/mmap.c:3251
__mmput+0x115/0x3c0 kernel/fork.c:1199
exit_mm+0x226/0x300 kernel/exit.c:563
do_exit+0x9f6/0x26a0 kernel/exit.c:856
do_group_exit+0x202/0x2b0 kernel/exit.c:1019
__do_sys_exit_group kernel/exit.c:1030 [inline]
__se_sys_exit_group kernel/exit.c:1028 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1028
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:0x7f5bef0b13b9
Code: Unable to access opcode bytes at 0x7f5bef0b138f.
RSP: 002b:00007ffcb9d797d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f5bef0b13b9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007f5bef12f370 R08: ffffffffffffffb8 R09: 00007ffcb9d7985c
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f5bef12f370
R13: 0000000000000000 R14: 00007f5bef12fde0 R15: 00007f5bef081930
</TASK>
BUG: scheduling while atomic: syz-executor151/6766/0x00000002
no locks held by syz-executor151/6766.
Modules linked in:
Preemption disabled at:
[<ffffffff817677fa>] is_module_text_address+0x1a/0x160 kernel/module/main.c:3097


---
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