syzbot


kernel panic: stack is corrupted in vprintk_emit

Status: upstream: reported C repro on 2024/08/16 13:07
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+4d2aaeff9eb5a2cfec70@syzkaller.appspotmail.com
First crash: 97d, last: 74d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ntfs3?] kernel panic: stack is corrupted in vprintk_emit 1 (9) 2024/09/10 07:08
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/11/05 07:51 19m retest repro upstream report log
2024/09/21 07:42 19m retest repro upstream OK log
2024/09/21 07:42 19m retest repro upstream OK log
2024/09/10 07:08 16m almaz.alexandrovich@paragon-software.com patch https://github.com/Paragon-Software-Group/linux-ntfs3.git master report log
2024/09/04 14:22 14m almaz.alexandrovich@paragon-software.com patch https://github.com/Paragon-Software-Group/linux-ntfs3.git master report log
2024/09/04 14:18 0m almaz.alexandrovich@paragon-software.com patch https://github.com/Paragon-Software-Group/linux-ntfs3.git master error
2024/09/02 12:45 15m almaz.alexandrovich@paragon-software.com patch upstream report log
2024/09/02 12:44 19m almaz.alexandrovich@paragon-software.com patch https://github.com/Paragon-Software-Group/linux-ntfs3.git master report log
2024/09/02 12:27 0m almaz.alexandrovich@paragon-software.com patch https://github.com/Paragon-Software-Group/linux-ntfs3.git master error
2024/08/27 07:27 21m eadavis@qq.com upstream report log

Sample crash report:
ntfs3: loop0: Different NTFS sector size (1024) and media sector size (512).
ntfs3: loop0: Failed to load $UpCase (-22).
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: vprintk_emit+0x764/0x770
CPU: 0 UID: 0 PID: 5459 Comm: syz-executor295 Not tainted 6.11.0-rc3-syzkaller-00156-gd7a5aa4b3c00 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:93 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119
 panic+0x349/0x860 kernel/panic.c:348
 __stack_chk_fail+0x15/0x20 kernel/panic.c:821
 vprintk_emit+0x764/0x770
 _printk+0xd5/0x120 kernel/printk/printk.c:2373
 ntfs_printk+0x3ad/0x420 fs/ntfs3/super.c:93
 ntfs_fill_super+0x2eb8/0x4730
 get_tree_bdev+0x3f7/0x570 fs/super.c:1635
 vfs_get_tree+0x90/0x2a0 fs/super.c:1800
 do_new_mount+0x2be/0xb40 fs/namespace.c:3472
 do_mount fs/namespace.c:3812 [inline]
 __do_sys_mount fs/namespace.c:4020 [inline]
 __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3997
 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:0x7fb031d0492a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 1e 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffce447eda8 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fb031d0492a
RDX: 000000002001f800 RSI: 000000002001f840 RDI: 00007ffce447edf0
RBP: 0000000000000004 R08: 00007ffce447ee30 R09: 000000000001f825
R10: 0000000000000801 R11: 0000000000000286 R12: 00007ffce447edf0
R13: 00007ffce447ee30 R14: 0000000000000003 R15: 0000000000200000
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (11):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/08/16 05:31 upstream d7a5aa4b3c00 e4bacdaf .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root kernel panic: stack is corrupted in vprintk_emit
2024/09/07 07:41 upstream b31c44928842 9750182a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in vprintk_emit
2024/08/19 03:24 upstream 47ac09b91bef e1c76ab2 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in vprintk_emit
2024/08/16 05:43 upstream d7a5aa4b3c00 e4bacdaf .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root kernel panic: stack is corrupted in vprintk_emit
2024/08/16 04:57 upstream d7a5aa4b3c00 e4bacdaf .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in vprintk_emit
2024/08/16 04:37 upstream d7a5aa4b3c00 e4bacdaf .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root kernel panic: stack is corrupted in vprintk_emit
2024/08/16 03:50 upstream d7a5aa4b3c00 e4bacdaf .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in vprintk_emit
2024/08/23 14:23 linux-next c79c85875f1a ce8a9099 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in vprintk_emit
2024/08/22 04:19 linux-next eb8c5ca373cb ca02180f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in vprintk_emit
2024/08/21 18:26 linux-next eb8c5ca373cb db5852f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in vprintk_emit
2024/08/21 04:08 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in vprintk_emit
* Struck through repros no longer work on HEAD.