[v5.15] WARNING in untrack_pfn

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=151ec592a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f546a5c7ff981a94
dashboard link: https://syzkaller.appspot.com/bug?extid=e68f8778d06d8e37ebbb
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=17e67a56a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1464afa2a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/601dfce79849/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b8e802138c25/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9b3b48ff5c05/bzImage-d54cfc42.xz

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

RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000002 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 431bde82d7b634db R14: 0000000000000001 R15: 0000000000000001
</TASK>
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3505 at arch/x86/mm/pat/memtype.c:1099 untrack_pfn+0x30e/0x490
Modules linked in:
CPU: 0 PID: 3505 Comm: syz-executor153 Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
RIP: 0010:untrack_pfn+0x30e/0x490 arch/x86/mm/pat/memtype.c:1099
Code: 8d 8c 24 a0 00 00 00 49 89 d8 e8 ad 82 7e 00 49 89 dd 89 c3 31 ff 89 c6 e8 5f 9b 45 00 85 db 0f 84 b2 00 00 00 e8 f2 97 45 00 <0f> 0b 48 bb 00 00 00 00 00 fc ff df eb 4f 48 b8 00 00 00 00 00 fc
RSP: 0018:ffffc9000253f500 EFLAGS: 00010293
RAX: ffffffff813a68ae RBX: 00000000ffffffea RCX: ffff8880143fbb80
RDX: 0000000000000000 RSI: 00000000ffffffea RDI: 0000000000000000
RBP: ffffc9000253f608 R08: ffffffff813a68a1 R09: ffffc9000253f480
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff110046a65ce
R13: ffffc9000253f580 R14: dffffc0000000000 R15: ffff888023532e70
FS: 00005555558aa380(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9eb8719a80 CR3: 000000002504c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
unmap_single_vma+0x1d8/0x2d0 mm/memory.c:1589
unmap_vmas+0x1f8/0x390 mm/memory.c:1642
exit_mmap+0x3b6/0x670 mm/mmap.c:3186
__mmput+0x112/0x3b0 kernel/fork.c:1118
mmput kernel/fork.c:1139 [inline]
dup_mm+0xe96/0x1230 kernel/fork.c:1473
copy_mm+0x101/0x190 kernel/fork.c:1509
copy_process+0x1816/0x3ef0 kernel/fork.c:2198
kernel_clone+0x210/0x960 kernel/fork.c:2601
__do_sys_clone kernel/fork.c:2718 [inline]
__se_sys_clone kernel/fork.c:2702 [inline]
__x64_sys_clone+0x23f/0x290 kernel/fork.c:2702
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:0x7f9eb86e6b79
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff29cb9b68 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007fff29cb9b80 RCX: 00007f9eb86e6b79
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000002 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 431bde82d7b634db R14: 0000000000000001 R15: 0000000000000001
</TASK>


---
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 bug is already fixed, 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 change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit d155df53f31068c3340733d586eb9b3ddfd70fc5
git tree: upstream
Author: Ma Wupeng <mawu...@huawei.com>
Date: Fri Feb 17 02:56:15 2023 +0000

x86/mm/pat: clear VM_PAT if copy_p4d_range failed

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=154dcb5ce80000

kernel config: https://syzkaller.appspot.com/x/.config?x=f546a5c7ff981a94
dashboard link: https://syzkaller.appspot.com/bug?extid=e68f8778d06d8e37ebbb

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17e67a56a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1464afa2a80000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection