[v6.6] kernel BUG in indx_clear

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 79643295eba1 Linux 6.6.157
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11048df9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7be9809cedd6b69c
dashboard link: https://syzkaller.appspot.com/bug?extid=06cac371b8fe4ccb0ce4
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a1af8d16581c/disk-79643295.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/66be9bddb1ec/vmlinux-79643295.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0329b316645d/bzImage-79643295.xz

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

------------[ cut here ]------------
kernel BUG at arch/x86/mm/physaddr.c:28!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5775 Comm: syz-executor Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:__phys_addr+0xea/0xf0 arch/x86/mm/physaddr.c:28
Code: a2 00 48 89 d8 eb 82 48 c7 c7 a0 4f fa 8c 48 89 c6 48 89 ca 48 89 c3 49 89 ce e8 81 58 2a 03 4c 89 f1 48 89 d8 e9 6c ff ff ff <0f> 0b 0f 0b 66 90 f3 0f 1e fa 53 48 89 fb 48 81 eb 00 00 00 80 48
RSP: 0018:ffffc900046ef958 EFLAGS: 00010206
RAX: deadc62d00000000 RBX: dead4ead80000000 RCX: 0000778000000000
RDX: 0000000000000000 RSI: ffffffff8b1d3b80 RDI: dead4ead00000000
RBP: 0000000000000001 R08: ffff88805bf970e0 R09: 0000000000000000
R10: ffff88805bf970d0 R11: ffffed100b7f2e1d R12: dffffc0000000000
R13: ffff88805bf971d8 R14: ffffffff82d0406e R15: dffffc0000000000
FS: 000055556d7fa500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555593645a38 CR3: 00000000610d8000 CR4: 00000000003506f0
Call Trace:
<TASK>
virt_to_folio include/linux/mm.h:1289 [inline]
kfree+0x43/0x1a0 mm/slab_common.c:1048
run_close fs/ntfs3/ntfs_fs.h:953 [inline]
indx_clear+0x3e/0x80 fs/ntfs3/index.c:870
ni_clear+0x211/0x460 fs/ntfs3/frecord.c:123
evict+0x4b7/0x8a0 fs/inode.c:705
__dentry_kill+0x412/0x630 fs/dcache.c:611
shrink_dentry_list+0x39a/0x6b0 fs/dcache.c:1206
shrink_dcache_parent+0xb2/0x3f0 fs/dcache.c:-1
do_one_tree+0x23/0xe0 fs/dcache.c:1686
shrink_dcache_for_umount+0x69/0x110 fs/dcache.c:1703
generic_shutdown_super+0x67/0x2b0 fs/super.c:665
kill_block_super+0x44/0x90 fs/super.c:1668
ntfs3_kill_sb+0x44/0x1b0 fs/ntfs3/super.c:1804
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x3d7/0x460 fs/namespace.c:1259
task_work_run+0x1d4/0x260 kernel/task_work.c:245
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:180
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:213
__syscall_exit_to_user_mode_work kernel/entry/common.c:294 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:305
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff66899f397
Code: a2 c7 05 5c 43 25 00 00 00 00 00 eb 96 e8 e1 12 00 00 90 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007fffea65ded8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007ff668a3448b RCX: 00007ff66899f397
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fffea65df90
RBP: 00007fffea65df90 R08: 00007fffea65ef90 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fffea65f020
R13: 00007ff668a3448b R14: 000000000007f6e4 R15: 00007fffea65f060
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__phys_addr+0xea/0xf0 arch/x86/mm/physaddr.c:28
Code: a2 00 48 89 d8 eb 82 48 c7 c7 a0 4f fa 8c 48 89 c6 48 89 ca 48 89 c3 49 89 ce e8 81 58 2a 03 4c 89 f1 48 89 d8 e9 6c ff ff ff <0f> 0b 0f 0b 66 90 f3 0f 1e fa 53 48 89 fb 48 81 eb 00 00 00 80 48
RSP: 0018:ffffc900046ef958 EFLAGS: 00010206
RAX: deadc62d00000000 RBX: dead4ead80000000 RCX: 0000778000000000
RDX: 0000000000000000 RSI: ffffffff8b1d3b80 RDI: dead4ead00000000
RBP: 0000000000000001 R08: ffff88805bf970e0 R09: 0000000000000000
R10: ffff88805bf970d0 R11: ffffed100b7f2e1d R12: dffffc0000000000
R13: ffff88805bf971d8 R14: ffffffff82d0406e R15: dffffc0000000000
FS: 000055556d7fa500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f3fec47950 CR3: 00000000610d8000 CR4: 00000000003506f0


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

syzbot has found a reproducer for the following issue on:

HEAD commit: 79643295eba1 Linux 6.6.157
git tree: linux-6.6.y

console output: https://syzkaller.appspot.com/x/log.txt?x=10025925580000

kernel config: https://syzkaller.appspot.com/x/.config?x=7be9809cedd6b69c
dashboard link: https://syzkaller.appspot.com/bug?extid=06cac371b8fe4ccb0ce4
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11927df9580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15927df9580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a1af8d16581c/disk-79643295.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/66be9bddb1ec/vmlinux-79643295.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0329b316645d/bzImage-79643295.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/27371f5b8439/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at arch/x86/mm/physaddr.c:28!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN

CPU: 0 PID: 5893 Comm: syz-executor Not tainted syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:__phys_addr+0xea/0xf0 arch/x86/mm/physaddr.c:28
Code: a2 00 48 89 d8 eb 82 48 c7 c7 a0 4f fa 8c 48 89 c6 48 89 ca 48 89 c3 49 89 ce e8 81 58 2a 03 4c 89 f1 48 89 d8 e9 6c ff ff ff <0f> 0b 0f 0b 66 90 f3 0f 1e fa 53 48 89 fb 48 81 eb 00 00 00 80 48

RSP: 0018:ffffc9000336f958 EFLAGS: 00010206

RAX: deadc62d00000000 RBX: dead4ead80000000 RCX: 0000778000000000
RDX: 0000000000000000 RSI: ffffffff8b1d3b80 RDI: dead4ead00000000

RBP: 0000000000000001 R08: ffff88805f5fb5e0 R09: 0000000000000000
R10: ffff88805f5fb5d0 R11: ffffed100bebf6bd R12: dffffc0000000000
R13: ffff88805f5fb6d8 R14: ffffffff82d0406e R15: dffffc0000000000
FS: 000055555d0a8500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007ffec0220ff0 CR3: 000000006c389000 CR4: 00000000003506f0

RIP: 0033:0x7f6a3079f397

Code: a2 c7 05 5c 43 25 00 00 00 00 00 eb 96 e8 e1 12 00 00 90 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8

RSP: 002b:00007ffec0221148 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f6a3083448b RCX: 00007f6a3079f397
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffec0221200
RBP: 00007ffec0221200 R08: 00007ffec0222200 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffec0222290
R13: 00007f6a3083448b R14: 000000000001ec96 R15: 00007ffec02222d0

</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__phys_addr+0xea/0xf0 arch/x86/mm/physaddr.c:28
Code: a2 00 48 89 d8 eb 82 48 c7 c7 a0 4f fa 8c 48 89 c6 48 89 ca 48 89 c3 49 89 ce e8 81 58 2a 03 4c 89 f1 48 89 d8 e9 6c ff ff ff <0f> 0b 0f 0b 66 90 f3 0f 1e fa 53 48 89 fb 48 81 eb 00 00 00 80 48

RSP: 0018:ffffc9000336f958 EFLAGS: 00010206

RAX: deadc62d00000000 RBX: dead4ead80000000 RCX: 0000778000000000
RDX: 0000000000000000 RSI: ffffffff8b1d3b80 RDI: dead4ead00000000

RBP: 0000000000000001 R08: ffff88805f5fb5e0 R09: 0000000000000000
R10: ffff88805f5fb5d0 R11: ffffed100bebf6bd R12: dffffc0000000000
R13: ffff88805f5fb6d8 R14: ffffffff82d0406e R15: dffffc0000000000
FS: 000055555d0a8500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 0000255235bb7ff8 CR3: 000000006c389000 CR4: 00000000003506f0


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