[v6.1] WARNING in untrack_pfn (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c2cbfe5f5122 Linux 6.1.51
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=166e8414680000
kernel config: https://syzkaller.appspot.com/x/.config?x=70c8f3bca951e933
dashboard link: https://syzkaller.appspot.com/bug?extid=2b0bae3d3650486d7c7d
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=156fd83fa80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11706d04680000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c6adf9ab3687/disk-c2cbfe5f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/250db52e24c6/vmlinux-c2cbfe5f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/294f52340eee/bzImage-c2cbfe5f.xz

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

RSP: 002b:00007ffe3e0f6b78 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007ffe3e0f6b90 RCX: 00007efcf9f34b79
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000002 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe3e0f6b8c
R13: 431bde82d7b634db R14: 0000000000000001 R15: 0000000000000001
</TASK>
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3547 at arch/x86/mm/pat/memtype.c:1107 untrack_pfn+0x30e/0x490
Modules linked in:
CPU: 0 PID: 3547 Comm: syz-executor414 Not tainted 6.1.51-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
RIP: 0010:untrack_pfn+0x30e/0x490 arch/x86/mm/pat/memtype.c:1107
Code: 8d 8c 24 a0 00 00 00 49 89 d8 e8 cd fd 8d 00 49 89 dd 89 c3 31 ff 89 c6 e8 4f 77 4b 00 85 db 0f 84 b2 00 00 00 e8 e2 73 4b 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:ffffc90003aaf380 EFLAGS: 00010293
RAX: ffffffff813e941e RBX: 00000000ffffffea RCX: ffff8880293a8000
RDX: 0000000000000000 RSI: 00000000ffffffea RDI: 0000000000000000
RBP: ffffc90003aaf490 R08: ffffffff813e9411 R09: ffffffff8a7abaa5
R10: 0000000000000003 R11: ffff8880293a8000 R12: 1ffff11003d40c51
R13: ffffc90003aaf400 R14: dffffc0000000000 R15: ffff88801ea06288
FS: 000055555567a380(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007efcf9f67a80 CR3: 00000000727e1000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
unmap_single_vma+0x1e3/0x290 mm/memory.c:1659
unmap_vmas+0x3c4/0x560 mm/memory.c:1720
exit_mmap+0x252/0x9f0 mm/mmap.c:3214
__mmput+0x115/0x3c0 kernel/fork.c:1191
mmput kernel/fork.c:1213 [inline]
dup_mm kernel/fork.c:1548 [inline]
copy_mm+0x1444/0x1990 kernel/fork.c:1581
copy_process+0x19a2/0x4020 kernel/fork.c:2259
kernel_clone+0x222/0x920 kernel/fork.c:2674
__do_sys_clone kernel/fork.c:2815 [inline]
__se_sys_clone kernel/fork.c:2799 [inline]
__x64_sys_clone+0x231/0x280 kernel/fork.c:2799
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+0x63/0xcd
RIP: 0033:0x7efcf9f34b79
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:00007ffe3e0f6b78 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007ffe3e0f6b90 RCX: 00007efcf9f34b79
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000002 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe3e0f6b8c
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 overwrite 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=14510ceae80000

kernel config: https://syzkaller.appspot.com/x/.config?x=70c8f3bca951e933
dashboard link: https://syzkaller.appspot.com/bug?extid=2b0bae3d3650486d7c7d

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156fd83fa80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11706d04680000

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

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