panic: vm_pager_assert_in: page ADDR is mapped

3 views
Skip to first unread message

syzbot

unread,
May 13, 2019, 2:11:10 PM5/13/19
to syzkaller-f...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 094736f0 Provide separate accounting for user-wired pages.
git tree: freebsd
console output: https://syzkaller.appspot.com/x/log.txt?x=13361830a00000
dashboard link: https://syzkaller.appspot.com/bug?extid=d741dc925ec66103a090

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

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

panic: vm_pager_assert_in: page 0xfffff8007f2c3f98 is mapped
cpuid = 0
time = 1557771053
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame
0xfffffe00212fe370
vpanic() at vpanic+0x1e0/frame 0xfffffe00212fe3d0
panic() at panic+0x43/frame 0xfffffe00212fe430
vm_pager_assert_in() at vm_pager_assert_in+0x198/frame 0xfffffe00212fe480
vm_pager_get_pages() at vm_pager_get_pages+0x3e/frame 0xfffffe00212fe4e0
vm_fault_hold() at vm_fault_hold+0x101b/frame 0xfffffe00212fe650
vm_fault() at vm_fault+0xad/frame 0xfffffe00212fe690
vm_map_wire_locked() at vm_map_wire_locked+0x72a/frame 0xfffffe00212fe770
vm_mmap_object() at vm_mmap_object+0x5ef/frame 0xfffffe00212fe7f0
vn_mmap() at vn_mmap+0x287/frame 0xfffffe00212fe890
kern_mmap() at kern_mmap+0x8a8/frame 0xfffffe00212fe950
sys_mmap() at sys_mmap+0x38/frame 0xfffffe00212fe980
amd64_syscall() at amd64_syscall+0x436/frame 0xfffffe00212feab0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe00212feab0
--- syscall (198, FreeBSD ELF64, nosys), rip = 0x41309a, rsp =
0x7fffdfffdf38, rbp = 0x6 ---
KDB: enter: panic
[ thread pid 1213 tid 100630 ]
Stopped at kdb_enter+0x6a: movq $0,kdb_why


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

Mark Johnston

unread,
May 14, 2019, 10:22:32 AM5/14/19
to syzbot, syzkaller-f...@googlegroups.com
#syz dup: panic: vm_object_vndeallocate: bad object reference count
Reply all
Reply to author
Forward
0 new messages