[v6.1] BUG: scheduling while atomic in exit_to_user_mode_loop

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4aa6747d9352 Linux 6.1.69
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=127c07cee80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1e9066810307299
dashboard link: https://syzkaller.appspot.com/bug?extid=d9de0b97ac13dcbb8aaf
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=12fdc061e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17444981e80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/90e712af4aa7/disk-4aa6747d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bdaad5d91499/vmlinux-4aa6747d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/157abc0d55dc/bzImage-4aa6747d.xz

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

BUG: scheduling while atomic: syz-executor283/3542/0x00000002
no locks held by syz-executor283/3542.
Modules linked in:
Preemption disabled at:
[<0000000000000000>] 0x0
Kernel panic - not syncing: scheduling while atomic: panic_on_warn set ...
CPU: 0 PID: 3542 Comm: syz-executor283 Not tainted 6.1.69-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
panic+0x318/0x75d kernel/panic.c:339
check_panic_on_warn+0x7e/0xa0 kernel/panic.c:235
__schedule_bug+0x1ba/0x220 kernel/sched/core.c:5788
schedule_debug kernel/sched/core.c:5817 [inline]
__schedule+0x14ed/0x4550 kernel/sched/core.c:6452
schedule+0xbf/0x180 kernel/sched/core.c:6634
exit_to_user_mode_loop+0x44/0x100 kernel/entry/common.c:159
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 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:0x7fa565a45973
Code: fe ff e9 41 ff ff ff 31 c9 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 80 3d 11 b7 07 00 00 49 89 ca 74 14 b8 3d 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 5d c3 0f 1f 40 00 48 83 ec 28 89 54 24 14 48
RSP: 002b:00007ffe6aad3e58 EFLAGS: 00000202 ORIG_RAX: 000000000000003d
RAX: 0000000000000000 RBX: 0000000000000de2 RCX: 00007fa565a45973
RDX: 0000000040000001 RSI: 00007ffe6aad3e6c RDI: 00000000ffffffff
RBP: 00000000000f4240 R08: 00007ffe6ab550b0 R09: 0000000000000010
R10: 0000000000000000 R11: 0000000000000202 R12: 000000000000c835
R13: 00007ffe6aad3e6c R14: 00007ffe6aad3e80 R15: 00007ffe6aad3e70
</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

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit f19a4050455aad847fb93f18dc1fe502eb60f989
git tree: upstream
Author: Jiri Olsa <jo...@kernel.org>
Date: Thu Dec 15 21:44:29 2022 +0000

bpf: Do cleanup in bpf_bprintf_cleanup only when needed

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14d29b09e80000

kernel config: https://syzkaller.appspot.com/x/.config?x=e1e9066810307299
dashboard link: https://syzkaller.appspot.com/bug?extid=d9de0b97ac13dcbb8aaf

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12fdc061e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17444981e80000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection