[v5.15] BUG: scheduling while atomic in exit_to_user_mode_loop

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6139f2a02fe0 Linux 5.15.148
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12381942180000
kernel config: https://syzkaller.appspot.com/x/.config?x=c170eb20d8be8542
dashboard link: https://syzkaller.appspot.com/bug?extid=db9b93e900b84e1aee87
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=1273ac68180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2ac68f24aed3/disk-6139f2a0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e8982a3768c5/vmlinux-6139f2a0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eb272dd019ce/bzImage-6139f2a0.xz

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

BUG: scheduling while atomic: udevd/2963/0x00000002
no locks held by udevd/2963.
Modules linked in:
Preemption disabled at:
[<ffffffff8174f806>] is_module_text_address+0x16/0x140 kernel/module.c:4758
Kernel panic - not syncing: scheduling while atomic: panic_on_warn set ...
CPU: 1 PID: 2963 Comm: udevd Not tainted 5.15.148-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
panic+0x318/0x84d kernel/panic.c:309
check_panic_on_warn+0x7e/0xa0 kernel/panic.c:229
__schedule_bug+0x1ba/0x220 kernel/sched/core.c:5570
schedule_debug kernel/sched/core.c:5599 [inline]
__schedule+0x138a/0x45b0 kernel/sched/core.c:6267
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
exit_to_user_mode_loop+0x44/0x130 kernel/entry/common.c:163
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fd362adc9a4
Code: 24 20 48 8d 44 24 30 48 89 44 24 28 64 8b 04 25 18 00 00 00 85 c0 75 2c 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 76 60 48 8b 15 55 a4 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffe50e99f10 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: 000000000000000c RBX: 00007ffe50e9a208 RCX: 00007fd362adc9a4
RDX: 0000000000080141 RSI: 0000562d089840d8 RDI: 00000000ffffff9c
RBP: 0000562d089840d8 R08: 00000000ffffffff R09: 0000000000000000
R10: 00000000000001a4 R11: 0000000000000246 R12: 0000000000080141
R13: ffffffffffffffff R14: 00000000ffffffff R15: 00000000ffffffff
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..


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