[v5.15] general protection fault in inode_wait_for_writeback (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 458ce51d0356 Linux 5.15.149
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=157ea09c180000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c016b4e71f1c777
dashboard link: https://syzkaller.appspot.com/bug?extid=7d9c7e735d83f1951f5f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16964ad8180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=172a5d64180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c84f9ea3bbab/disk-458ce51d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/70bdbf46c57d/vmlinux-458ce51d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/73fc8d1364f3/bzImage-458ce51d.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/a8afb8f9ce50/mount_0.gz

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

ntfs3: loop0: Different NTFS' sector size (2048) and media sector size (512)
general protection fault, probably for non-canonical address 0x457c3ac974252983: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 4910 Comm: syz-executor189 Not tainted 5.15.149-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
RIP: 0010:_raw_spin_lock+0x29/0x40 kernel/locking/spinlock.c:154
Code: 00 53 48 89 fb bf 01 00 00 00 e8 c2 ca 30 f7 48 8d 7b 18 31 f6 31 d2 31 c9 41 b8 01 00 00 00 45 31 c9 ff 74 24 08 e8 06 16 3c <f7> 48 83 c4 08 48 89 df 5b e9 99 8a 3d f7 66 0f 1f 84 00 00 00 00
RSP: 0000:ffffc90004c47928 EFLAGS: 00010246
RAX: 457c3ac974252a00 RBX: ffff888073eef178 RCX: ffffffff816340f2
RDX: dffffc0000000000 RSI: ffffffff8a8b27a0 RDI: ffffffff8ad88e40
RBP: ffffc90004c47a40 R08: dffffc0000000000 R09: fffffbfff1f7a632
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888073eef178
R13: dffffc0000000000 R14: ffff888073eef0f0 R15: ffffc90004c47980
FS: 0000555556098380(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f44d3510920 CR3: 0000000024248000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
spin_lock include/linux/spinlock.h:363 [inline]
inode_wait_for_writeback+0x89/0x280 fs/fs-writeback.c:1527
evict+0x277/0x620 fs/inode.c:584
ntfs_fill_super+0x3c50/0x4460 fs/ntfs3/super.c:1185
get_tree_bdev+0x3fe/0x620 fs/super.c:1312
vfs_get_tree+0x88/0x270 fs/super.c:1517
do_new_mount+0x2ba/0xb40 fs/namespace.c:3005
do_mount fs/namespace.c:3348 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3533
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:0x7f44d3510a5a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 0e 06 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe054f45d8 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f44d3510a5a
RDX: 000000002001f380 RSI: 000000002001f3c0 RDI: 00007ffe054f4620
RBP: 0000000000000004 R08: 00007ffe054f4660 R09: 000000000001f346
R10: 0000000000000000 R11: 0000000000000286 R12: 00007ffe054f4620
R13: 00007ffe054f4660 R14: 0000000000200000 R15: 0000000000000003
</TASK>
Modules linked in:
---[ end trace a8c7c7f8f5134baf ]---
RIP: 0010:__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
RIP: 0010:_raw_spin_lock+0x29/0x40 kernel/locking/spinlock.c:154
Code: 00 53 48 89 fb bf 01 00 00 00 e8 c2 ca 30 f7 48 8d 7b 18 31 f6 31 d2 31 c9 41 b8 01 00 00 00 45 31 c9 ff 74 24 08 e8 06 16 3c <f7> 48 83 c4 08 48 89 df 5b e9 99 8a 3d f7 66 0f 1f 84 00 00 00 00
RSP: 0000:ffffc90004c47928 EFLAGS: 00010246
RAX: 457c3ac974252a00 RBX: ffff888073eef178 RCX: ffffffff816340f2
RDX: dffffc0000000000 RSI: ffffffff8a8b27a0 RDI: ffffffff8ad88e40
RBP: ffffc90004c47a40 R08: dffffc0000000000 R09: fffffbfff1f7a632
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888073eef178
R13: dffffc0000000000 R14: ffff888073eef0f0 R15: ffffc90004c47980
FS: 0000555556098380(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f44d3510920 CR3: 0000000024248000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 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