[moderation] [kernel?] kernel panic: corrupted stack end in do_idle

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 02c438bbfffe Merge tag 'for-6.10-tag' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13c58f0a980000
kernel config: https://syzkaller.appspot.com/x/.config?x=aeb4d28a6349ece
dashboard link: https://syzkaller.appspot.com/bug?extid=d6a7ff9066d29d3b4f4f
compiler: arm-linux-gnueabi-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm
CC: [linux-...@vger.kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/8ead8862021c/non_bootable_disk-02c438bb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7970cbd0ad33/vmlinux-02c438bb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f935f6903b84/zImage-02c438bb.xz

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

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.9.0-syzkaller #0
Hardware name: ARM-Versatile Express
Call trace:
[<818d5778>] (dump_backtrace) from [<818d5874>] (show_stack+0x18/0x1c arch/arm/kernel/traps.c:257)
r7:00000000 r6:82622d44 r5:00000000 r4:81fe1590
[<818d585c>] (show_stack) from [<818f2e84>] (__dump_stack lib/dump_stack.c:88 [inline])
[<818d585c>] (show_stack) from [<818f2e84>] (dump_stack_lvl+0x54/0x7c lib/dump_stack.c:114)
[<818f2e30>] (dump_stack_lvl) from [<818f2ec4>] (dump_stack+0x18/0x1c lib/dump_stack.c:123)
r5:00000000 r4:8285fd18
[<818f2eac>] (dump_stack) from [<818d631c>] (panic+0x120/0x358 kernel/panic.c:347)
[<818d61fc>] (panic) from [<818f7a6c>] (schedule_debug kernel/sched/core.c:5962 [inline])
[<818d61fc>] (panic) from [<818f7a6c>] (__schedule+0xbd4/0xbd8 kernel/sched/core.c:6628)
r3:57ac6e9d r2:8260001c r1:81fe1590 r0:81fd4eac
r7:824b6440
[<818f6e98>] (__schedule) from [<818f7fe4>] (schedule_idle+0x24/0x68 kernel/sched/core.c:6863)
r10:00000000 r9:00000000 r8:00000000 r7:8260c5f8 r6:8261ad80 r5:8260c5d0
r4:8261ad80
[<818f7fc0>] (schedule_idle) from [<8029b7b0>] (do_idle+0x19c/0x2cc kernel/sched/idle.c:360)
r5:8260c5d0 r4:00000000
[<8029b614>] (do_idle) from [<8029bc14>] (cpu_startup_entry+0x30/0x34 kernel/sched/idle.c:430)
r10:8261a8b0 r9:820f7964 r8:8260c580 r7:00000000 r6:deffc061 r5:82625cbc
r4:000000ec
[<8029bbe4>] (cpu_startup_entry) from [<818f51d0>] (kernel_init+0x0/0x138 init/main.c:747)
[<818f50f0>] (rest_init) from [<82401398>] (start_kernel+0x75c/0x778 init/main.c:1103)
[<82400c3c>] (start_kernel) from [<00000000>] (0x0)
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 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