syzbot


BUG: Bad page map

Status: auto-obsoleted due to no activity on 2023/06/05 15:46
Reported-by: syzbot+000823e04b3d4c93be41@syzkaller.appspotmail.com
First crash: 417d, last: 417d
Similar bugs (14)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 BUG: Bad page map (3) 1 649d 649d 0/1 auto-obsoleted due to no activity on 2022/11/15 21:40
upstream BUG: Bad page map (5) mm io-uring C 35 469d 727d 22/26 fixed on 2023/02/24 13:50
linux-4.19 BUG: Bad page map (2) 10 835d 1016d 0/1 auto-closed as invalid on 2022/05/13 11:22
upstream BUG: Bad page map (2) mm syz 127 2061d 2117d 0/26 closed as invalid on 2018/09/05 12:51
android-5-10 BUG: Bad page map (2) 1 199d 199d 0/2 auto-obsoleted due to no activity on 2024/01/10 02:50
upstream BUG: Bad page map mm 1 2120d 2120d 0/26 closed as invalid on 2018/07/08 13:28
upstream BUG: Bad page map (3) kernel 4 1931d 2056d 0/26 auto-closed as invalid on 2019/07/13 00:02
linux-4.19 BUG: Bad page map 2 1333d 1391d 0/1 auto-closed as invalid on 2021/01/01 08:20
upstream BUG: Bad page map (7) mm C done 19 209d 231d 25/26 fixed on 2023/12/21 03:45
android-54 BUG: Bad page map (2) 7 198d 316d 0/2 auto-obsoleted due to no activity on 2024/01/10 18:32
upstream BUG: Bad page map (4) mm 39 877d 1513d 0/26 auto-closed as invalid on 2022/04/02 04:25
linux-4.14 BUG: Bad page map 1 1378d 1378d 0/1 auto-closed as invalid on 2020/11/16 16:05
upstream BUG: Bad page map (6) mm 1 383d 379d 0/26 auto-obsoleted due to no activity on 2023/07/09 13:20
android-54 BUG: Bad page map 1 612d 612d 0/2 auto-obsoleted due to no activity on 2022/12/23 04:05

Sample crash report:
swap_info_get: Bad swap file entry 3ffffff7fffff
BUG: Bad page map in process syz-executor.4  pte:100000000 pmd:130c70067
addr:0000000020201000 vm_flags:00100077 anon_vma:ffff888111fd60a8 mapping:0000000000000000 index:20201
file:(null) fault:0x0 mmap:0x0 readpage:0x0
CPU: 0 PID: 29749 Comm: syz-executor.4 Not tainted 5.10.161-syzkaller-00019-g416c4356f372 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack_lvl+0x1e2/0x24b lib/dump_stack.c:118
 dump_stack+0x15/0x17 lib/dump_stack.c:135
 print_bad_pte+0x57f/0x5a0 mm/memory.c:582
 zap_pte_range mm/memory.c:1375 [inline]
 zap_pmd_range mm/memory.c:1444 [inline]
 zap_pud_range mm/memory.c:1473 [inline]
 zap_p4d_range mm/memory.c:1494 [inline]
 unmap_page_range+0x17d7/0x2070 mm/memory.c:1516
 unmap_single_vma mm/memory.c:1562 [inline]
 unmap_vmas+0x3d4/0x5b0 mm/memory.c:1594
 exit_mmap+0x2f9/0x5c0 mm/mmap.c:3341
 __mmput+0x95/0x2c0 kernel/fork.c:1133
 mmput+0x4b/0x50 kernel/fork.c:1154
 exit_mm+0x5cd/0x790 kernel/exit.c:489
 do_exit+0x5f2/0x2340 kernel/exit.c:800
 do_group_exit+0x13a/0x300 kernel/exit.c:910
 get_signal+0xe17/0x1440 kernel/signal.c:2780
 arch_do_signal+0x8e/0x650 arch/x86/kernel/signal.c:805
 exit_to_user_mode_loop+0xa3/0xe0 kernel/entry/common.c:161
 exit_to_user_mode_prepare kernel/entry/common.c:191 [inline]
 syscall_exit_to_user_mode+0x77/0xa0 kernel/entry/common.c:266
 do_syscall_64+0x40/0x70 arch/x86/entry/common.c:56
 entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7f65610d00f9
Code: Unable to access opcode bytes at RIP 0x7f65610d00cf.
RSP: 002b:00007f655fe22218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007f65611f0058 RCX: 00007f65610d00f9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f65611f0058
RBP: 00007f65611f0050 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f65611f005c
R13: 00007ffeb33390ef R14: 00007f655fe22300 R15: 0000000000022000

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/03/07 15:44 android12-5.10-lts 416c4356f372 d7ea8bc4 .config console log report info ci2-android-5-10 BUG: Bad page map
* Struck through repros no longer work on HEAD.