[v6.6] BUG: Bad page state in copy_page_range
0 views
Skip to first unread message
syzbot
Dec 1, 2025, 10:49:30 AM12/1/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 4791134e4aeb Linux 6.6.118
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=119f4b6f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=67cdf06e16f3eeb0d99d
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ca168ecfe887/disk-4791134e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/adda86b1a76b/vmlinux-4791134e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cc2019969cb7/bzImage-4791134e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+67cdf0...@syzkaller.appspotmail.com
BUG: Bad page state in process syz.2.1043 pfn:7bc0d
page:ffffea0001ef0340 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x7bc0d
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xfffffdff(table)
raw: 00fff00000000000 ffffea0001654c08 ffffc9000bd9f560 0000000000000000
raw: 0000000000000000 ffff888075d0a0c0 00000000fffffdff 0000000000000000
page dumped because: nonzero mapcount
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x540dc0(GFP_USER|__GFP_COMP|__GFP_ZERO|__GFP_ACCOUNT), pid 8690, tgid 8690 (syz-executor), ts 203870470554, free_ts 203855510578
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x1cd/0x210 mm/page_alloc.c:1554
prep_new_page mm/page_alloc.c:1561 [inline]
get_page_from_freelist+0x195c/0x19f0 mm/page_alloc.c:3191
__alloc_pages+0x1e3/0x460 mm/page_alloc.c:4457
pagetable_alloc include/linux/mm.h:2900 [inline]
__pte_alloc_one include/asm-generic/pgalloc.h:68 [inline]
pte_alloc_one+0x89/0x540 arch/x86/mm/pgtable.c:33
__pte_alloc+0x22/0x2a0 mm/memory.c:438
copy_pte_range mm/memory.c:1029 [inline]
copy_pmd_range mm/memory.c:1168 [inline]
copy_pud_range mm/memory.c:1205 [inline]
copy_p4d_range mm/memory.c:1229 [inline]
copy_page_range+0x2d72/0x3600 mm/memory.c:1323
dup_mmap kernel/fork.c:764 [inline]
dup_mm kernel/fork.c:1692 [inline]
copy_mm+0x11a8/0x1ca0 kernel/fork.c:1741
copy_process+0x16d3/0x3d70 kernel/fork.c:2506
kernel_clone+0x21b/0x840 kernel/fork.c:2914
__do_sys_clone kernel/fork.c:3057 [inline]
__se_sys_clone kernel/fork.c:3041 [inline]
__x64_sys_clone+0x18c/0x1e0 kernel/fork.c:3041
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1154 [inline]
free_unref_page_prepare+0x7ce/0x8e0 mm/page_alloc.c:2336
free_unref_page_list+0xbe/0x860 mm/page_alloc.c:2475
release_pages+0x1fa0/0x2220 mm/swap.c:1022
__folio_batch_release+0x71/0xe0 mm/swap.c:1042
folio_batch_release include/linux/pagevec.h:83 [inline]
truncate_inode_pages_range+0x358/0xf00 mm/truncate.c:396
evict+0x499/0x870 fs/inode.c:707
erofs_put_super+0x7b/0x150 fs/erofs/super.c:815
generic_shutdown_super+0x134/0x2b0 fs/super.c:693
kill_block_super+0x44/0x90 fs/super.c:1660
erofs_kill_sb+0x4c/0x140 fs/erofs/super.c:794
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1259
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
Modules linked in:
CPU: 1 PID: 9184 Comm: syz.2.1043 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
bad_page+0x14b/0x170 mm/page_alloc.c:512
free_page_is_bad mm/page_alloc.c:961 [inline]
free_pages_prepare mm/page_alloc.c:1146 [inline]
free_unref_page_prepare+0x887/0x8e0 mm/page_alloc.c:2336
free_unref_page_list+0xbe/0x860 mm/page_alloc.c:2475
release_pages+0x1fa0/0x2220 mm/swap.c:1022
folios_put include/linux/mm.h:1548 [inline]
folio_batch_move_lru+0x5bb/0x6b0 mm/swap.c:216
lru_add_drain_cpu+0x10e/0x8c0 mm/swap.c:644
lru_add_drain+0x121/0x3e0 mm/swap.c:744
exit_mmap+0x1cb/0xb50 mm/mmap.c:3297
__mmput+0x118/0x3c0 kernel/fork.c:1355
exit_mm+0x1da/0x2c0 kernel/exit.c:569
do_exit+0x88e/0x23c0 kernel/exit.c:870
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x1400 kernel/signal.c:2902
arch_do_signal_or_restart+0x9c/0x7b0 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f54b258f749
Code: Unable to access opcode bytes at 0x7f54b258f71f.
RSP: 002b:00007f54b33cc038 EFLAGS: 00000246 ORIG_RAX: 000000000000010f
RAX: 0000000000000001 RBX: 00007f54b27e5fa0 RCX: 00007f54b258f749
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000200000000000
RBP: 00007f54b2613f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f54b27e6038 R14: 00007f54b27e5fa0 R15: 00007ffcd64bd738
</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 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 found the following issue on:
HEAD commit: 4791134e4aeb Linux 6.6.118
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=119f4b6f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=67cdf06e16f3eeb0d99d
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ca168ecfe887/disk-4791134e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/adda86b1a76b/vmlinux-4791134e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cc2019969cb7/bzImage-4791134e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+67cdf0...@syzkaller.appspotmail.com
BUG: Bad page state in process syz.2.1043 pfn:7bc0d
page:ffffea0001ef0340 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x7bc0d
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xfffffdff(table)
raw: 00fff00000000000 ffffea0001654c08 ffffc9000bd9f560 0000000000000000
raw: 0000000000000000 ffff888075d0a0c0 00000000fffffdff 0000000000000000
page dumped because: nonzero mapcount
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x540dc0(GFP_USER|__GFP_COMP|__GFP_ZERO|__GFP_ACCOUNT), pid 8690, tgid 8690 (syz-executor), ts 203870470554, free_ts 203855510578
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x1cd/0x210 mm/page_alloc.c:1554
prep_new_page mm/page_alloc.c:1561 [inline]
get_page_from_freelist+0x195c/0x19f0 mm/page_alloc.c:3191
__alloc_pages+0x1e3/0x460 mm/page_alloc.c:4457
pagetable_alloc include/linux/mm.h:2900 [inline]
__pte_alloc_one include/asm-generic/pgalloc.h:68 [inline]
pte_alloc_one+0x89/0x540 arch/x86/mm/pgtable.c:33
__pte_alloc+0x22/0x2a0 mm/memory.c:438
copy_pte_range mm/memory.c:1029 [inline]
copy_pmd_range mm/memory.c:1168 [inline]
copy_pud_range mm/memory.c:1205 [inline]
copy_p4d_range mm/memory.c:1229 [inline]
copy_page_range+0x2d72/0x3600 mm/memory.c:1323
dup_mmap kernel/fork.c:764 [inline]
dup_mm kernel/fork.c:1692 [inline]
copy_mm+0x11a8/0x1ca0 kernel/fork.c:1741
copy_process+0x16d3/0x3d70 kernel/fork.c:2506
kernel_clone+0x21b/0x840 kernel/fork.c:2914
__do_sys_clone kernel/fork.c:3057 [inline]
__se_sys_clone kernel/fork.c:3041 [inline]
__x64_sys_clone+0x18c/0x1e0 kernel/fork.c:3041
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1154 [inline]
free_unref_page_prepare+0x7ce/0x8e0 mm/page_alloc.c:2336
free_unref_page_list+0xbe/0x860 mm/page_alloc.c:2475
release_pages+0x1fa0/0x2220 mm/swap.c:1022
__folio_batch_release+0x71/0xe0 mm/swap.c:1042
folio_batch_release include/linux/pagevec.h:83 [inline]
truncate_inode_pages_range+0x358/0xf00 mm/truncate.c:396
evict+0x499/0x870 fs/inode.c:707
erofs_put_super+0x7b/0x150 fs/erofs/super.c:815
generic_shutdown_super+0x134/0x2b0 fs/super.c:693
kill_block_super+0x44/0x90 fs/super.c:1660
erofs_kill_sb+0x4c/0x140 fs/erofs/super.c:794
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1259
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
Modules linked in:
CPU: 1 PID: 9184 Comm: syz.2.1043 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
bad_page+0x14b/0x170 mm/page_alloc.c:512
free_page_is_bad mm/page_alloc.c:961 [inline]
free_pages_prepare mm/page_alloc.c:1146 [inline]
free_unref_page_prepare+0x887/0x8e0 mm/page_alloc.c:2336
free_unref_page_list+0xbe/0x860 mm/page_alloc.c:2475
release_pages+0x1fa0/0x2220 mm/swap.c:1022
folios_put include/linux/mm.h:1548 [inline]
folio_batch_move_lru+0x5bb/0x6b0 mm/swap.c:216
lru_add_drain_cpu+0x10e/0x8c0 mm/swap.c:644
lru_add_drain+0x121/0x3e0 mm/swap.c:744
exit_mmap+0x1cb/0xb50 mm/mmap.c:3297
__mmput+0x118/0x3c0 kernel/fork.c:1355
exit_mm+0x1da/0x2c0 kernel/exit.c:569
do_exit+0x88e/0x23c0 kernel/exit.c:870
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x1400 kernel/signal.c:2902
arch_do_signal_or_restart+0x9c/0x7b0 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f54b258f749
Code: Unable to access opcode bytes at 0x7f54b258f71f.
RSP: 002b:00007f54b33cc038 EFLAGS: 00000246 ORIG_RAX: 000000000000010f
RAX: 0000000000000001 RBX: 00007f54b27e5fa0 RCX: 00007f54b258f749
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000200000000000
RBP: 00007f54b2613f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f54b27e6038 R14: 00007f54b27e5fa0 R15: 00007ffcd64bd738
</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 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
Reply all
Reply to author
Forward
0 new messages