syzbot


panic: pmap active ADDR

Status: fixed on 2021/05/14 02:24
Reported-by: syzbot+0aa7c2bec74c4066c36f@syzkaller.appspotmail.com
Fix commit: 9246b3090cbc fork: Suspend other threads if both RFPROC and RFMEM are not set
First crash: 551d, last: 514d

Sample crash report:
panic: pmap active 0xfffffe0094c4f120
cpuid = 1
time = 1617723805
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame 0xfffffe00949b47c0
vpanic() at vpanic+0x1c7/frame 0xfffffe00949b4820
panic() at panic+0x43/frame 0xfffffe00949b4880
pmap_remove_pages() at pmap_remove_pages+0x1775/frame 0xfffffe00949b49f0
vmspace_exit() at vmspace_exit+0x139/frame 0xfffffe00949b4a30
exit1() at exit1+0x7f5/frame 0xfffffe00949b4aa0
sys_sys_exit() at sys_sys_exit+0xd/frame 0xfffffe00949b4ab0
amd64_syscall() at amd64_syscall+0x247/frame 0xfffffe00949b4bf0
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00949b4bf0
--- syscall (1, FreeBSD ELF64, sys_sys_exit), rip = 0x29583a, rsp = 0x7fffdffdc508, rbp = 0x7fffdffdc520 ---
KDB: enter: panic
[ thread pid 3322 tid 101804 ]
Stopped at      kdb_enter+0x67: movq    $0,0x143d69e(%rip)
db> 
db> 

Crashes (5):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-freebsd-main 2021/04/06 15:48 freebsd-src e5fc416c2855 6a81331a log report syz C panic: pmap active ADDR
ci-freebsd-main 2021/04/06 15:35 freebsd-src e5fc416c2855 6a81331a log report panic: pmap active ADDR
ci-freebsd-i386 2021/05/06 13:13 freebsd-src 49c894ddced5 06c27ff5 log report panic: pmap active ADDR
ci-freebsd-i386 2021/04/30 23:29 freebsd-src e010d20032c8 77e2b668 log report panic: pmap active ADDR
ci-freebsd-i386 2021/03/30 05:26 freebsd-src 4d5460a720c5 6a81331a log report panic: pmap active ADDR
* Struck through repros no longer work on HEAD.