panic: Most recently used by temp

2 views
Skip to first unread message

syzbot

unread,
May 9, 2019, 8:46:08 AM5/9/19
to syzkaller-f...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: c150a0f6 Existense of PCB route caching doesn't allow us t..
git tree: freebsd
console output: https://syzkaller.appspot.com/x/log.txt?x=17ac8394a00000
dashboard link: https://syzkaller.appspot.com/bug?extid=b48d3bc31487d9343757

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+b48d3b...@syzkaller.appspotmail.com

panic: Most recently used by temp

cpuid = 0
time = 300
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame
0xfffffe0023149220
vpanic() at vpanic+0x1e0/frame 0xfffffe0023149280
panic() at panic+0x43/frame 0xfffffe00231492e0
mtrash_ctor() at mtrash_ctor+0xed/frame 0xfffffe0023149320
uma_zalloc_arg() at uma_zalloc_arg+0x1036/frame 0xfffffe00231493d0
malloc() at malloc+0xe1/frame 0xfffffe0023149440
elf64_load_file() at elf64_load_file+0x6d/frame 0xfffffe00231494b0
exec_elf64_imgact() at exec_elf64_imgact+0x1aa2/frame 0xfffffe00231495b0
kern_execve() at kern_execve+0x7d8/frame 0xfffffe0023149900
sys_execve() at sys_execve+0x79/frame 0xfffffe0023149980
amd64_syscall() at amd64_syscall+0x436/frame 0xfffffe0023149ab0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe0023149ab0
--- syscall (59, FreeBSD ELF64, sys_execve), rip = 0x8003bc3ca, rsp =
0x7fffffffe408, rbp = 0x7fffffffe510 ---
KDB: enter: panic
[ thread pid 3349 tid 100376 ]
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.

syzbot

unread,
Oct 25, 2019, 4:51:07 AM10/25/19
to syzkaller-f...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages