Message-ID: <000000000000a96781061f0a1165@google.com>
Date: Tue, 06 Aug 2024 13:59:26 -0700
From: syzbot <syzbot+1e65605d6233841d7c3c@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [kernel?] kernel panic: corrupted stack end in do_idle

Hello,

syzbot found the following issue on:

HEAD commit:    b446a2dae984 Merge tag 'linux_kselftest-fixes-6.11-rc3' of..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12b2759d980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=692f298d4e1a1b64
dashboard link: https://syzkaller.appspot.com/bug?extid=1e65605d6233841d7c3c
compiler:       arm-linux-gnueabi-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm

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-b446a2da.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/15ff7610068d/vmlinux-b446a2da.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ef3c5eb94167/zImage-b446a2da.xz

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

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.11.0-rc2-syzkaller #0
Hardware name: ARM-Versatile Express
Call trace: 
[<81953848>] (dump_backtrace) from [<81953944>] (show_stack+0x18/0x1c arch/arm/kernel/traps.c:257)
 r7:00000000 r6:826228c4 r5:00000000 r4:8200ba34
[<8195392c>] (show_stack) from [<81971618>] (__dump_stack lib/dump_stack.c:93 [inline])
[<8195392c>] (show_stack) from [<81971618>] (dump_stack_lvl+0x54/0x7c lib/dump_stack.c:119)
[<819715c4>] (dump_stack_lvl) from [<81971658>] (dump_stack+0x18/0x1c lib/dump_stack.c:128)
 r5:00000000 r4:8286bd18
[<81971640>] (dump_stack) from [<819543ec>] (panic+0x120/0x358 kernel/panic.c:348)
[<819542cc>] (panic) from [<81975e8c>] (schedule_debug kernel/sched/core.c:5745 [inline])
[<819542cc>] (panic) from [<81975e8c>] (__schedule+0xb68/0xb6c kernel/sched/core.c:6411)
 r3:57ac6e9d r2:00000000 r1:8200ba34 r0:81fff164
 r7:824b9340
[<81975324>] (__schedule) from [<819761a8>] (schedule_idle+0x24/0x68 kernel/sched/core.c:6647)
 r10:00000000 r9:00000000 r8:00000000 r7:8260c5fc r6:8261ae40 r5:8260c5d0
 r4:8261ae40
[<81976184>] (schedule_idle) from [<80297f48>] (do_idle+0x19c/0x2cc kernel/sched/idle.c:354)
 r5:8260c5d0 r4:00000000
[<80297dac>] (do_idle) from [<802983ac>] (cpu_startup_entry+0x30/0x34 kernel/sched/idle.c:424)
 r10:8261a970 r9:82128eb4 r8:8260c580 r7:00000000 r6:deffc061 r5:82625864
 r4:000000ee
[<8029837c>] (cpu_startup_entry) from [<81973968>] (kernel_init+0x0/0x138 init/main.c:747)
[<81973888>] (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 syzkaller@...glegroups.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

Powered by blists - more mailing lists