[mm?] BUG: Bad page map (6)
7 views
Skip to first unread message
syzbot
Apr 14, 2023, 9:29:43 AM4/14/23
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 09a9639e56c0 Linux 6.3-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15f0b7d7c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=90aa79dcf599c3f1
dashboard link: https://syzkaller.appspot.com/bug?extid=bd7013d0c6474dfad88b
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bd7013...@syzkaller.appspotmail.com
BUG: Bad page map in process syz-executor.1 pte:800fffffff899875 pmd:4ca80067
addr:00007ffd8dc73000 vm_flags:00100173 anon_vma:ffff8880159cf990 mapping:0000000000000000 index:7fffffffd
file:(null) fault:0x0 mmap:0x0 read_folio:0x0
CPU: 2 PID: 5192 Comm: syz-executor.1 Not tainted 6.3.0-rc6-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x136/0x150 lib/dump_stack.c:106
print_bad_pte+0x4e2/0x770 mm/memory.c:519
vm_normal_page+0x110/0x2a0 mm/memory.c:590
can_change_pte_writable+0x229/0x7f0 mm/mprotect.c:69
do_numa_page mm/memory.c:4696 [inline]
handle_pte_fault mm/memory.c:4930 [inline]
__handle_mm_fault+0x2c78/0x3e60 mm/memory.c:5065
handle_mm_fault+0x2ba/0x9c0 mm/memory.c:5211
do_user_addr_fault+0x475/0x1230 arch/x86/mm/fault.c:1407
handle_page_fault arch/x86/mm/fault.c:1498 [inline]
exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1554
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7fdcdc6b0e94
Code: 3c 24 48 89 4c 24 18 e8 aa e7 ff ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 8b 74 24 0c 8b 3c 24 b8 e6 00 00 00 0f 05 44 89 c7 <48> 89 04 24 e8 e3 e7 ff ff 48 8b 04 24 eb 97 66 2e 0f 1f 84 00 00
RSP: 002b:00007ffd8dc73bf0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000004ab6 RCX: 00007fdcdc6b0e91
RDX: 00007ffd8dc73c30 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007ffd8dc73cbc R08: 0000000000000000 R09: 00007ffd8dcd7080
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 000000000006b8eb R14: 0000000000000000 R15: 00007ffd8dc73d20
</TASK>
BUG: Bad page map in process syz-executor.1 pte:800fffffff899875 pmd:4ca80067
addr:00007ffd8dc73000 vm_flags:00100173 anon_vma:ffff8880159cf990 mapping:0000000000000000 index:7fffffffd
file:(null) fault:0x0 mmap:0x0 read_folio:0x0
CPU: 2 PID: 5192 Comm: syz-executor.1 Tainted: G B 6.3.0-rc6-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x136/0x150 lib/dump_stack.c:106
print_bad_pte+0x4e2/0x770 mm/memory.c:519
vm_normal_page+0x110/0x2a0 mm/memory.c:590
do_numa_page mm/memory.c:4699 [inline]
handle_pte_fault mm/memory.c:4930 [inline]
__handle_mm_fault+0x1c57/0x3e60 mm/memory.c:5065
handle_mm_fault+0x2ba/0x9c0 mm/memory.c:5211
do_user_addr_fault+0x475/0x1230 arch/x86/mm/fault.c:1407
handle_page_fault arch/x86/mm/fault.c:1498 [inline]
exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1554
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7fdcdc6b0e94
Code: 3c 24 48 89 4c 24 18 e8 aa e7 ff ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 8b 74 24 0c 8b 3c 24 b8 e6 00 00 00 0f 05 44 89 c7 <48> 89 04 24 e8 e3 e7 ff ff 48 8b 04 24 eb 97 66 2e 0f 1f 84 00 00
RSP: 002b:00007ffd8dc73bf0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000004ab6 RCX: 00007fdcdc6b0e91
RDX: 00007ffd8dc73c30 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007ffd8dc73cbc R08: 0000000000000000 R09: 00007ffd8dcd7080
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 000000000006b8eb R14: 0000000000000000 R15: 00007ffd8dc73d20
</TASK>
_swap_info_get: Bad swap file entry 3803d0464cfffdff
BUG: Bad page map in process syz-executor.1 pte:705f736600040048 pmd:4ca80067
addr:00007ffd8dc54000 vm_flags:00100173 anon_vma:ffff8880159cf990 mapping:0000000000000000 index:7ffffffde
file:(null) fault:0x0 mmap:0x0 read_folio:0x0
CPU: 3 PID: 5192 Comm: syz-executor.1 Tainted: G B D 6.3.0-rc6-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x136/0x150 lib/dump_stack.c:106
print_bad_pte+0x4e2/0x770 mm/memory.c:519
zap_pte_range mm/memory.c:1447 [inline]
zap_pmd_range mm/memory.c:1536 [inline]
zap_pud_range mm/memory.c:1565 [inline]
zap_p4d_range mm/memory.c:1586 [inline]
unmap_page_range+0x2cc4/0x3ce0 mm/memory.c:1607
unmap_single_vma+0x194/0x2a0 mm/memory.c:1653
unmap_vmas+0x234/0x380 mm/memory.c:1692
exit_mmap+0x190/0x7f0 mm/mmap.c:3031
__mmput+0x128/0x4c0 kernel/fork.c:1207
mmput+0x60/0x70 kernel/fork.c:1229
exit_mm kernel/exit.c:563 [inline]
do_exit+0x9d7/0x2960 kernel/exit.c:856
do_group_exit+0xd4/0x2a0 kernel/exit.c:1019
get_signal+0x2315/0x25b0 kernel/signal.c:2859
arch_do_signal_or_restart+0x79/0x5c0 arch/x86/kernel/signal.c:306
exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
exit_to_user_mode_prepare+0x11f/0x240 kernel/entry/common.c:204
irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:310
exc_page_fault+0xc0/0x170 arch/x86/mm/fault.c:1557
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7fdcdc6b0e94
Code: Unable to access opcode bytes at 0x7fdcdc6b0e6a.
RSP: 002b:00007ffd8dc73bf0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000004ab6 RCX: 00007fdcdc6b0e91
RDX: 00007ffd8dc73c30 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007ffd8dc73cbc R08: 0000000000000000 R09: 00007ffd8dcd7080
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 000000000006b8eb R14: 0000000000000000 R15: 00007ffd8dc73d20
</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.
syzbot found the following issue on:
HEAD commit: 09a9639e56c0 Linux 6.3-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15f0b7d7c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=90aa79dcf599c3f1
dashboard link: https://syzkaller.appspot.com/bug?extid=bd7013d0c6474dfad88b
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bd7013...@syzkaller.appspotmail.com
BUG: Bad page map in process syz-executor.1 pte:800fffffff899875 pmd:4ca80067
addr:00007ffd8dc73000 vm_flags:00100173 anon_vma:ffff8880159cf990 mapping:0000000000000000 index:7fffffffd
file:(null) fault:0x0 mmap:0x0 read_folio:0x0
CPU: 2 PID: 5192 Comm: syz-executor.1 Not tainted 6.3.0-rc6-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x136/0x150 lib/dump_stack.c:106
print_bad_pte+0x4e2/0x770 mm/memory.c:519
vm_normal_page+0x110/0x2a0 mm/memory.c:590
can_change_pte_writable+0x229/0x7f0 mm/mprotect.c:69
do_numa_page mm/memory.c:4696 [inline]
handle_pte_fault mm/memory.c:4930 [inline]
__handle_mm_fault+0x2c78/0x3e60 mm/memory.c:5065
handle_mm_fault+0x2ba/0x9c0 mm/memory.c:5211
do_user_addr_fault+0x475/0x1230 arch/x86/mm/fault.c:1407
handle_page_fault arch/x86/mm/fault.c:1498 [inline]
exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1554
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7fdcdc6b0e94
Code: 3c 24 48 89 4c 24 18 e8 aa e7 ff ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 8b 74 24 0c 8b 3c 24 b8 e6 00 00 00 0f 05 44 89 c7 <48> 89 04 24 e8 e3 e7 ff ff 48 8b 04 24 eb 97 66 2e 0f 1f 84 00 00
RSP: 002b:00007ffd8dc73bf0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000004ab6 RCX: 00007fdcdc6b0e91
RDX: 00007ffd8dc73c30 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007ffd8dc73cbc R08: 0000000000000000 R09: 00007ffd8dcd7080
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 000000000006b8eb R14: 0000000000000000 R15: 00007ffd8dc73d20
</TASK>
BUG: Bad page map in process syz-executor.1 pte:800fffffff899875 pmd:4ca80067
addr:00007ffd8dc73000 vm_flags:00100173 anon_vma:ffff8880159cf990 mapping:0000000000000000 index:7fffffffd
file:(null) fault:0x0 mmap:0x0 read_folio:0x0
CPU: 2 PID: 5192 Comm: syz-executor.1 Tainted: G B 6.3.0-rc6-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x136/0x150 lib/dump_stack.c:106
print_bad_pte+0x4e2/0x770 mm/memory.c:519
vm_normal_page+0x110/0x2a0 mm/memory.c:590
do_numa_page mm/memory.c:4699 [inline]
handle_pte_fault mm/memory.c:4930 [inline]
__handle_mm_fault+0x1c57/0x3e60 mm/memory.c:5065
handle_mm_fault+0x2ba/0x9c0 mm/memory.c:5211
do_user_addr_fault+0x475/0x1230 arch/x86/mm/fault.c:1407
handle_page_fault arch/x86/mm/fault.c:1498 [inline]
exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1554
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7fdcdc6b0e94
Code: 3c 24 48 89 4c 24 18 e8 aa e7 ff ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 8b 74 24 0c 8b 3c 24 b8 e6 00 00 00 0f 05 44 89 c7 <48> 89 04 24 e8 e3 e7 ff ff 48 8b 04 24 eb 97 66 2e 0f 1f 84 00 00
RSP: 002b:00007ffd8dc73bf0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000004ab6 RCX: 00007fdcdc6b0e91
RDX: 00007ffd8dc73c30 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007ffd8dc73cbc R08: 0000000000000000 R09: 00007ffd8dcd7080
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 000000000006b8eb R14: 0000000000000000 R15: 00007ffd8dc73d20
</TASK>
_swap_info_get: Bad swap file entry 3803d0464cfffdff
BUG: Bad page map in process syz-executor.1 pte:705f736600040048 pmd:4ca80067
addr:00007ffd8dc54000 vm_flags:00100173 anon_vma:ffff8880159cf990 mapping:0000000000000000 index:7ffffffde
file:(null) fault:0x0 mmap:0x0 read_folio:0x0
CPU: 3 PID: 5192 Comm: syz-executor.1 Tainted: G B D 6.3.0-rc6-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x136/0x150 lib/dump_stack.c:106
print_bad_pte+0x4e2/0x770 mm/memory.c:519
zap_pte_range mm/memory.c:1447 [inline]
zap_pmd_range mm/memory.c:1536 [inline]
zap_pud_range mm/memory.c:1565 [inline]
zap_p4d_range mm/memory.c:1586 [inline]
unmap_page_range+0x2cc4/0x3ce0 mm/memory.c:1607
unmap_single_vma+0x194/0x2a0 mm/memory.c:1653
unmap_vmas+0x234/0x380 mm/memory.c:1692
exit_mmap+0x190/0x7f0 mm/mmap.c:3031
__mmput+0x128/0x4c0 kernel/fork.c:1207
mmput+0x60/0x70 kernel/fork.c:1229
exit_mm kernel/exit.c:563 [inline]
do_exit+0x9d7/0x2960 kernel/exit.c:856
do_group_exit+0xd4/0x2a0 kernel/exit.c:1019
get_signal+0x2315/0x25b0 kernel/signal.c:2859
arch_do_signal_or_restart+0x79/0x5c0 arch/x86/kernel/signal.c:306
exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
exit_to_user_mode_prepare+0x11f/0x240 kernel/entry/common.c:204
irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:310
exc_page_fault+0xc0/0x170 arch/x86/mm/fault.c:1557
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7fdcdc6b0e94
Code: Unable to access opcode bytes at 0x7fdcdc6b0e6a.
RSP: 002b:00007ffd8dc73bf0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000004ab6 RCX: 00007fdcdc6b0e91
RDX: 00007ffd8dc73c30 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007ffd8dc73cbc R08: 0000000000000000 R09: 00007ffd8dcd7080
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 000000000006b8eb R14: 0000000000000000 R15: 00007ffd8dc73d20
</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.
syzbot
Jul 9, 2023, 9:20:49 AM7/9/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages