syzbot


kernel panic: stack is corrupted in debug_object_activate

Status: upstream: reported on 2024/12/27 02:58
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+352ebcaffdbde4edf230@syzkaller.appspotmail.com
First crash: 274d, last: 9d14h
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ntfs3?] kernel panic: stack is corrupted in debug_object_activate 0 (1) 2024/12/27 02:58

Sample crash report:
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: debug_object_activate+0x3bb/0x420 lib/debugobjects.c:-1
CPU: 0 UID: 0 PID: 5330 Comm: syz.0.0 Not tainted 6.16.0-rc3-syzkaller-00057-g92ca6c498a5e #0 PREEMPT(full) 
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_lvl+0x99/0x250 lib/dump_stack.c:120
 panic+0x2db/0x790 kernel/panic.c:382
 __stack_chk_fail+0x26/0x30 kernel/panic.c:869
 debug_object_activate+0x3bb/0x420 lib/debugobjects.c:-1
 debug_rcu_head_queue kernel/rcu/rcu.h:236 [inline]
 __call_rcu_common kernel/rcu/tree.c:3079 [inline]
 call_rcu+0xaa/0x9c0 kernel/rcu/tree.c:3214
 destroy_inode fs/inode.c:401 [inline]
 evict+0x847/0x9c0 fs/inode.c:834
 ntfs_fill_super+0x3913/0x40c0 fs/ntfs3/super.c:1513
 get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1681
 vfs_get_tree+0x92/0x2b0 fs/super.c:1804
 do_new_mount+0x24a/0xa40 fs/namespace.c:3885
 do_mount fs/namespace.c:4222 [inline]
 __do_sys_mount fs/namespace.c:4433 [inline]
 __se_sys_mount+0x317/0x410 fs/namespace.c:4410
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f633fb900ca
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:00007f6340a57e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f6340a57ef0 RCX: 00007f633fb900ca
RDX: 000020000001f800 RSI: 000020000001f840 RDI: 00007f6340a57eb0
RBP: 000020000001f800 R08: 00007f6340a57ef0 R09: 0000000000000010
R10: 0000000000000010 R11: 0000000000000246 R12: 000020000001f840
R13: 00007f6340a57eb0 R14: 000000000001f814 R15: 0000200000000040
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (13):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/26 06:52 upstream 92ca6c498a5e 26d77996 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2025/04/01 02:11 upstream 609706855d90 36d76a97 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2025/03/10 01:44 upstream 1110ce6a1e34 163f510d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2025/02/27 11:55 upstream 5394eea10651 6a8fcbc4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2025/02/11 07:50 upstream febbc555cf0f 43f51a00 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2025/02/01 07:04 upstream 69e858e0b8b2 aa47157c .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2025/01/21 00:54 upstream ffd294d346d1 6e87cfa2 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2025/01/18 14:28 upstream 595523945be0 f2cb035c .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2024/12/27 02:57 upstream d6ef8b40d075 d3ccff63 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2024/12/23 11:10 upstream 4bbf9020becb 444551c4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2024/12/10 05:59 upstream 7cb1b4663150 deb72877 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2024/10/12 21:18 upstream 09f6b0c8904b 084d8178 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
2024/10/04 10:00 upstream 3840cbe24cf0 d7906eff .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in debug_object_activate
* Struck through repros no longer work on HEAD.