[moderation] [ntfs3?] kernel panic: stack is corrupted in __lock_acquire (6)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f4345f05c0df Merge tag 'block-6.9-20240510' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1539583f180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7144b4fe7fbf5900
dashboard link: https://syzkaller.appspot.com/bug?extid=0799e3da3a519a99be40
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
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 (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-f4345f05.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/614ec2f69250/vmlinux-f4345f05.xz
kernel image: https://storage.googleapis.com/syzbot-assets/634f18189631/bzImage-f4345f05.xz

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

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __lock_acquire+0x2de4/0x3b30 kernel/locking/lockdep.c:5168
CPU: 2 PID: 9196 Comm: syz-executor.1 Not tainted 6.9.0-rc7-syzkaller-00136-gf4345f05c0df #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x3d/0x1f0 lib/dump_stack.c:114
panic+0x6f5/0x7a0 kernel/panic.c:348
__stack_chk_fail+0x15/0x20 kernel/panic.c:780
__lock_acquire+0x2de4/0x3b30 kernel/locking/lockdep.c:5168
lock_acquire kernel/locking/lockdep.c:5754 [inline]
lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5719
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
inode_get_bytes+0x1f/0xa0 fs/stat.c:849
attr_set_size+0x2223/0x2c60 fs/ntfs3/attrib.c:814
ntfs_set_size+0x13d/0x220 fs/ntfs3/inode.c:845
ntfs_extend+0x401/0x570 fs/ntfs3/file.c:335
ntfs_file_write_iter+0x433/0x2050 fs/ntfs3/file.c:1115
call_write_iter include/linux/fs.h:2110 [inline]
iter_file_splice_write+0x906/0x10b0 fs/splice.c:743
do_splice_from fs/splice.c:941 [inline]
direct_splice_actor+0x19b/0x6d0 fs/splice.c:1164
splice_direct_to_actor+0x346/0xa40 fs/splice.c:1108
do_splice_direct_actor fs/splice.c:1207 [inline]
do_splice_direct+0x17e/0x250 fs/splice.c:1233
do_sendfile+0xaa8/0xdb0 fs/read_write.c:1295
__do_sys_sendfile64 fs/read_write.c:1362 [inline]
__se_sys_sendfile64 fs/read_write.c:1348 [inline]
__x64_sys_sendfile64+0x1da/0x220 fs/read_write.c:1348
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcf/0x260 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7faa13c7dd69
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007faa1494c0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007faa13dabf80 RCX: 00007faa13c7dd69
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000005
RBP: 00007faa13cca49e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000100000001 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007faa13dabf80 R15: 00007ffccf740e58
</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 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