[moderation] [ntfs3?] kernel panic: stack is corrupted in rt_spin_lock

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 479058002c32 Merge tag 'ata-6.17-rc1-fixes' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12ecd6a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=943d6f7b1ddd8799
dashboard link: https://syzkaller.appspot.com/bug?extid=c02effcfcba04e3d6234
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
CC: [almaz.ale...@paragon-software.com linux-...@vger.kernel.org nt...@lists.linux.dev]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7226b9adab95/disk-47905800.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b10c6c12e41f/vmlinux-47905800.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7e99b92d1763/bzImage-47905800.xz

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

loop3: detected capacity change from 0 to 4096
ntfs3(loop3): 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: 0 UID: 0 PID: 8003 Comm: syz.3.324 Tainted: G W 6.16.0-syzkaller-11852-g479058002c32 #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+0x92/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:0x7f4781a6038a
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:00007f477f8bde68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f477f8bdef0 RCX: 00007f4781a6038a
RDX: 0000200000000140 RSI: 0000200000000980 RDI: 00007f477f8bdeb0
RBP: 0000200000000140 R08: 00007f477f8bdef0 R09: 0000000002004404
R10: 0000000002004404 R11: 0000000000000246 R12: 0000200000000980
R13: 00007f477f8bdeb0 R14: 000000000001f883 R15: 0000200000000780
</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 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

[syzbot]

Sending this report to the next reporting stage.