Hello,
syzbot found the following issue on:
HEAD commit: 9d6bde853685 Linux 5.15.112
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1490ae5a280000
kernel config:
https://syzkaller.appspot.com/x/.config?x=a61e8195d8bdf36e
dashboard link:
https://syzkaller.appspot.com/bug?extid=36d9632fc4eac47cba41
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/b65d6c2ec328/disk-9d6bde85.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/cf811ebac37b/vmlinux-9d6bde85.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/b2f32fdecf97/bzImage-9d6bde85.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+36d963...@syzkaller.appspotmail.com
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_acquire+0x4e9/0x4f0
CPU: 1 PID: 28362 Comm: syz-executor.4 Not tainted 5.15.112-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
panic+0x318/0x84d kernel/panic.c:309
__stack_chk_fail+0x10/0x10 kernel/panic.c:753
lock_acquire+0x4e9/0x4f0
__raw_spin_lock_irq include/linux/spinlock_api_smp.h:128 [inline]
_raw_spin_lock_irq+0xcf/0x110 kernel/locking/spinlock.c:170
spin_lock_irq include/linux/spinlock.h:388 [inline]
truncate_inode_pages_final+0x5f/0x90 mm/truncate.c:456
ntfs_evict_inode+0x18/0xb0 fs/ntfs3/inode.c:1772
evict+0x2a4/0x620 fs/inode.c:587
ntfs_fill_super+0x3c3f/0x4450 fs/ntfs3/super.c:1185
get_tree_bdev+0x3fe/0x620 fs/super.c:1303
vfs_get_tree+0x88/0x270 fs/super.c:1508
do_new_mount+0x28b/0xad0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f656f0d769a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 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:00007f656d647f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 000000000001f329 RCX: 00007f656f0d769a
RDX: 000000002001f340 RSI: 000000002001f380 RDI: 00007f656d647fe0
RBP: 00007f656d648020 R08: 00007f656d648020 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 000000002001f340
R13: 000000002001f380 R14: 00007f656d647fe0 R15: 000000002001f3c0
</TASK>
Kernel Offset: disabled
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
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup