assert "(pg->pg_flags & (PQ_INACTIVE|PQ_ACTIVE)) == NUM" failed in uvm_page.c

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d004c0aeba6f Update show rib mem stats now that we have pe..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=126fb992580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=f3c3aa16434bc13e3138

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/01be3807f2ba/disk-d004c0ae.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/23a2f4ec7e38/bsd-d004c0ae.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cf7f4cb33c51/kernel-d004c0ae.xz

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

panic: kernel diagnostic assertion "(pg->pg_flags & (PQ_INACTIVE|PQ_ACTIVE)) == 0" failed: file "/syzkaller/managers/main/kernel/sys/uvm/uvm_page.c", line 1309
Starting stack trace...
panic(ffffffff83379cc9) at panic+0x1ba sys/kern/subr_prf.c:229
__assert(ffffffff833b8c73,ffffffff833a4157,51d,ffffffff833e9a32) at __assert+0x29 sys/kern/subr_prf.c:-1
uvm_pageactivate(fffffd8006e0ac80) at uvm_pageactivate+0x1e2 sys/uvm/uvm_page.c:1306
uvm_fault_lower(ffff80002a85d660,ffff80002a85d698,ffff80002a85d5e0) at uvm_fault_lower+0x22a sys/uvm/uvm_fault.c:1391
uvm_fault(fffffd806cc64d00,200000000000,0,2) at uvm_fault+0x241 sys/uvm/uvm_fault.c:-1
upageflttrap(ffff80002a85d800,200000000040) at upageflttrap+0xa0 sys/arch/amd64/amd64/trap.c:192
usertrap(ffff80002a85d800) at usertrap+0x413 sys/arch/amd64/amd64/trap.c:632
recall_trap() at recall_trap+0x8
end of kernel
end trace frame: 0x77609cb3cac0, count: 249
End of stack trace.


---
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