[moderation] [ntfs3?] invalid opcode in zero_user_segments

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4a5df3796467 Merge tag 'mm-hotfixes-stable-2024-11-16-15-3..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17375b5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=95b7d4b29182ed62
dashboard link: https://syzkaller.appspot.com/bug?extid=7fa8e17b5fbacb4ae883
compiler: Debian clang version 15.0.6, 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/7feb34a89c2a/non_bootable_disk-4a5df379.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cb509a18129b/vmlinux-4a5df379.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4a4deaeedf54/bzImage-4a5df379.xz

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

Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5328 Comm: syz.0.0 Not tainted 6.12.0-rc7-syzkaller-00212-g4a5df3796467 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:zero_user_segments+0x28b/0x290 include/linux/highmem.h:275
Code: 05 02 e9 47 fe ff ff e8 e3 f0 a3 fe 89 ea be 00 10 00 00 48 c7 c7 b0 5c cf 8e e8 50 4a 05 02 e9 d3 fe ff ff e8 c6 f0 a3 fe 90 <0f> 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3
RSP: 0018:ffffc9000cf5ed00 EFLAGS: 00010293
RAX: ffffffff82f0f94a RBX: ffffea0001137000 RCX: ffff888000e30000
RDX: 0000000000000000 RSI: 0000000000001782 RDI: 0000000000001000
RBP: 0000000000001000 R08: ffffffff82f0f785 R09: 1ffffd4000226e00
R10: dffffc0000000000 R11: fffff94000226e01 R12: 0000000000001782
R13: 0000000000000000 R14: 1ffffd4000226e00 R15: 0000000000001782
FS: 00007f4be7aa46c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4be6cf0130 CR3: 00000000008a4000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
folio_zero_range include/linux/highmem.h:647 [inline]
ntfs_extend_initialized_size+0x50b/0x950 fs/ntfs3/file.c:225
ntfs_extend+0x578/0xad0 fs/ntfs3/file.c:413
ntfs_file_write_iter+0x403/0x7a0 fs/ntfs3/file.c:1254
__kernel_write_iter+0x42a/0x940 fs/read_write.c:616
__kernel_write+0x120/0x180 fs/read_write.c:636
__dump_emit+0x237/0x360 fs/coredump.c:807
writenote+0x221/0x3b0 fs/binfmt_elf.c:1463


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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.