[<prev] [next>] [day] [month] [year] [list]
Message-ID: <68a17e86.050a0220.e29e5.0060.GAE@google.com>
Date: Sun, 17 Aug 2025 00:02:30 -0700
From: syzbot <syzbot+37fb05d692157c085e99@...kaller.appspotmail.com>
To: almaz.alexandrovich@...agon-software.com, linux-kernel@...r.kernel.org,
ntfs3@...ts.linux.dev, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [ntfs3?] kernel panic: stack is corrupted in rt_spin_lock
Hello,
syzbot found the following issue on:
HEAD commit: 90d970cade8e Merge tag 'ata-ata-6.17-rc2' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1077baf0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=98e114f4eb77e551
dashboard link: https://syzkaller.appspot.com/bug?extid=37fb05d692157c085e99
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143173a2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/db659c83faa4/disk-90d970ca.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1d736b8a5536/vmlinux-90d970ca.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3ed0655ad73d/bzImage-90d970ca.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/11f86826b4f2/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+37fb05d692157c085e99@...kaller.appspotmail.com
loop0: detected capacity change f[ 188.250627][ T7465] 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: rt_spin_lock+0x2b8/0x2c0 kernel/locking/spinlock_rt.c:-1
CPU: 1 UID: 0 PID: 7465 Comm: syz.0.701 Tainted: G W 6.17.0-rc1-syzkaller-00211-g90d970cade8e #0 PREEMPT_{RT,(full)}
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
<TASK>
dump_stack_lvl+0x99/0x250 lib/dump_stack.c:120
vpanic+0x281/0x750 kernel/panic.c:430
panic+0xb9/0xc0 kernel/panic.c:566
__stack_chk_fail+0x26/0x30 kernel/panic.c:929
rt_spin_lock+0x2b8/0x2c0 kernel/locking/spinlock_rt.c:-1
spin_lock_irq include/linux/spinlock_rt.h:93 [inline]
__filemap_add_folio+0x964/0x11c0 mm/filemap.c:884
filemap_add_folio+0xd5/0x270 mm/filemap.c:969
do_read_cache_folio+0x1de/0x560 mm/filemap.c:3924
do_read_cache_page mm/filemap.c:4023 [inline]
read_cache_page+0x5d/0x170 mm/filemap.c:4032
read_mapping_page include/linux/pagemap.h:985 [inline]
inode_read_data+0xa7/0x480 fs/ntfs3/inode.c:1054
ntfs_fill_super+0x39c8/0x40b0 fs/ntfs3/super.c:1533
get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1692
vfs_get_tree+0x8f/0x2b0 fs/super.c:1815
do_new_mount+0x2a2/0x9e0 fs/namespace.c:3805
do_mount fs/namespace.c:4133 [inline]
__do_sys_mount fs/namespace.c:4344 [inline]
__se_sys_mount+0x317/0x410 fs/namespace.c:4321
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:0x7f2805e8038a
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:00007f28054ede68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f28054edef0 RCX: 00007f2805e8038a
RDX: 00002000000000c0 RSI: 00002000000001c0 RDI: 00007f28054edeb0
RBP: 00002000000000c0 R08: 00007f28054edef0 R09: 0000000000800014
R10: 0000000000800014 R11: 0000000000000246 R12: 00002000000001c0
R13: 00007f28054edeb0 R14: 000000000001f854 R15: 00002000000004c0
</TASK>
Kernel Offset: disabled
---
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 syzkaller@...glegroups.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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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
Powered by blists - more mailing lists