[v6.1] kernel panic: stack is corrupted in __schedule (2)

6 views
Skip to first unread message

syzbot

unread,
Oct 18, 2024, 8:59:27 PM10/18/24
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 54d90d17e8ce Linux 6.1.113
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17c7d830580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3757166a6a7e985
dashboard link: https://syzkaller.appspot.com/bug?extid=378e7654dfd63c527586
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/911f6b814ba2/disk-54d90d17.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/171ad8824108/vmlinux-54d90d17.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ec19432ca7b0/bzImage-54d90d17.xz

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

loop1: detected capacity change from 0 to 4096
ntfs3: loop1: Different NTFS' sector size (1024) and media sector size (512)
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x2051/0x4570
CPU: 1 PID: 5141 Comm: syz.1.249 Not tainted 6.1.113-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
panic+0x318/0x764 kernel/panic.c:339
__stack_chk_fail+0x10/0x10 kernel/panic.c:767
__schedule+0x2051/0x4570
preempt_schedule_irq+0xf7/0x1c0 kernel/sched/core.c:6870
irqentry_exit+0x53/0x80 kernel/entry/common.c:439
asm_sysvec_reschedule_ipi+0x16/0x20 arch/x86/include/asm/idtentry.h:696
RIP: 0010:preempt_count_add+0x2/0x180 kernel/sched/core.c:5697
Code: 0c 24 80 e1 07 80 c1 03 38 c1 7c 97 48 8b 3c 24 e8 c3 8e 83 00 eb 8c e9 f2 fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 66 90 41 57 <41> 56 53 89 fb 48 c7 c0 60 71 33 97 48 c1 e8 03 49 bf 00 00 00 00
RSP: 0018:ffffc9000355fa00 EFLAGS: 00000283
RAX: ffffffff8a9b9cb8 RBX: ffff888071583dd8 RCX: 0000000000040000
RDX: ffffc90011988000 RSI: 000000000001338e RDI: 0000000000000001
RBP: ffff888071583d50 R08: ffffffff8a9b9c5c R09: ffffed100e2b07ec
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888071583f58
R13: 0000000000000a00 R14: ffff888071583dd8 R15: ffff888071583f58
__raw_spin_lock include/linux/spinlock_api_smp.h:132 [inline]
_raw_spin_lock+0xe/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
_atomic_dec_and_lock+0xb0/0x130 lib/dec_and_lock.c:28
iput+0x83/0x980 fs/inode.c:1848
ntfs_fill_super+0x3c01/0x4410 fs/ntfs3/super.c:1190
get_tree_bdev+0x3fe/0x620 fs/super.c:1366
vfs_get_tree+0x88/0x270 fs/super.c:1573
do_new_mount+0x2ba/0xb40 fs/namespace.c:3056
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3584
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa524f7f79a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa524dfee68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fa524dfeef0 RCX: 00007fa524f7f79a
RDX: 000000002001f800 RSI: 000000002001f840 RDI: 00007fa524dfeeb0
RBP: 000000002001f800 R08: 00007fa524dfeef0 R09: 0000000000800004
R10: 0000000000800004 R11: 0000000000000246 R12: 000000002001f840
R13: 00007fa524dfeeb0 R14: 000000000001f802 R15: 0000000020000100
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
----------------
Code disassembly (best guess):
0: 0c 24 or $0x24,%al
2: 80 e1 07 and $0x7,%cl
5: 80 c1 03 add $0x3,%cl
8: 38 c1 cmp %al,%cl
a: 7c 97 jl 0xffffffa3
c: 48 8b 3c 24 mov (%rsp),%rdi
10: e8 c3 8e 83 00 call 0x838ed8
15: eb 8c jmp 0xffffffa3
17: e9 f2 fe ff ff jmp 0xffffff0e
1c: 66 2e 0f 1f 84 00 00 cs nopw 0x0(%rax,%rax,1)
23: 00 00 00
26: 66 90 xchg %ax,%ax
28: 41 57 push %r15
* 2a: 41 56 push %r14 <-- trapping instruction
2c: 53 push %rbx
2d: 89 fb mov %edi,%ebx
2f: 48 c7 c0 60 71 33 97 mov $0xffffffff97337160,%rax
36: 48 c1 e8 03 shr $0x3,%rax
3a: 49 rex.WB
3b: bf 00 00 00 00 mov $0x0,%edi


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

syzbot

unread,
Apr 23, 2025, 8:04:21 PM4/23/25
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages