[moderation] [kernel?] kernel panic: stack is corrupted in preempt_schedule_irq

0 views
Skip to first unread message

syzbot

unread,
Jun 14, 2024, 8:17:25 PM (12 days ago) Jun 14
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d35b2284e966 Add linux-next specific files for 20240607
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=156c4196980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d8bf5cd6bcca7343
dashboard link: https://syzkaller.appspot.com/bug?extid=84d8d7f7a60706cde24b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [linux-...@vger.kernel.org lu...@kernel.org pet...@infradead.org tg...@linutronix.de]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e0055a00a2cb/disk-d35b2284.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/192cbb8cf833/vmlinux-d35b2284.xz
kernel image: https://storage.googleapis.com/syzbot-assets/57804c9c9319/bzImage-d35b2284.xz

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

loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Different NTFS sector size (1024) and media sector size (512).
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: preempt_schedule_irq+0x1b5/0x1c0
CPU: 1 PID: 5474 Comm: syz-executor.0 Not tainted 6.10.0-rc2-next-20240607-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:91 [inline]
dump_stack_lvl+0x241/0x360 lib/dump_stack.c:117
panic+0x349/0x870 kernel/panic.c:348
__stack_chk_fail+0x15/0x20 kernel/panic.c:830
preempt_schedule_irq+0x1b5/0x1c0
irqentry_exit+0x5e/0x90 kernel/entry/common.c:354
asm_sysvec_reschedule_ipi+0x1a/0x20 arch/x86/include/asm/idtentry.h:707
RIP: 0010:__might_resched+0x17a/0x780
Code: 00 00 00 00 fc ff df 48 89 44 24 38 0f b6 04 10 84 c0 0f 85 87 04 00 00 41 8b 45 00 c1 e0 08 01 d8 44 39 e0 0f 85 d6 00 00 00 <44> 89 64 24 1c 48 8d bc 24 a0 00 00 00 48 89 fb 48 c1 eb 03 80 3c
RSP: 0018:ffffc900099a77e0 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff88802a160000
RDX: dffffc0000000000 RSI: ffff88802a160000 RDI: ffffffff8c200e00
RBP: ffffc900099a78f8 R08: ffffffff81cde7a2 R09: 1ffffd40002e4bf0
R10: dffffc0000000000 R11: fffff940002e4bf1 R12: 0000000000000000
R13: ffff88802a160444 R14: 00000000000000a9 R15: 1ffff92001334f04
kmap include/linux/highmem-internal.h:169 [inline]
ntfs_map_page+0x45/0x60 fs/ntfs3/ntfs_fs.h:925
ntfs_fill_super+0x3b49/0x4a20 fs/ntfs3/super.c:1440
get_tree_bdev+0x3f7/0x570 fs/super.c:1615
vfs_get_tree+0x90/0x2a0 fs/super.c:1780
do_new_mount+0x2be/0xb40 fs/namespace.c:3352
do_mount fs/namespace.c:3692 [inline]
__do_sys_mount fs/namespace.c:3898 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3875
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1895e7e66a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f1896b8def8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f1896b8df80 RCX: 00007f1895e7e66a
RDX: 000000002001f800 RSI: 0000000020000040 RDI: 00007f1896b8df40
RBP: 000000002001f800 R08: 00007f1896b8df80 R09: 0000000000000002
R10: 0000000000000002 R11: 0000000000000206 R12: 0000000020000040
R13: 00007f1896b8df40 R14: 000000000001f82a R15: 00000000200002c0
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
----------------
Code disassembly (best guess), 6 bytes skipped:
0: df 48 89 fisttps -0x77(%rax)
3: 44 24 38 rex.R and $0x38,%al
6: 0f b6 04 10 movzbl (%rax,%rdx,1),%eax
a: 84 c0 test %al,%al
c: 0f 85 87 04 00 00 jne 0x499
12: 41 8b 45 00 mov 0x0(%r13),%eax
16: c1 e0 08 shl $0x8,%eax
19: 01 d8 add %ebx,%eax
1b: 44 39 e0 cmp %r12d,%eax
1e: 0f 85 d6 00 00 00 jne 0xfa
* 24: 44 89 64 24 1c mov %r12d,0x1c(%rsp) <-- trapping instruction
29: 48 8d bc 24 a0 00 00 lea 0xa0(%rsp),%rdi
30: 00
31: 48 89 fb mov %rdi,%rbx
34: 48 c1 eb 03 shr $0x3,%rbx
38: 80 .byte 0x80
39: 3c .byte 0x3c


---
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
Reply all
Reply to author
Forward
0 new messages