syzbot


panic: Most recently used by ip6opt

Status: auto-closed as invalid on 2019/10/25 08:44
Reported-by: syzbot+97a8da4c64ca7b3f1305@syzkaller.appspotmail.com
First crash: 1868d, last: 1838d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
freebsd panic: Most recently used by ip6opt (2) syz 4 1553d 1598d 2/2 fixed on 2020/03/20 00:05

Sample crash report:
panic: Most recently used by ip6opt

cpuid = 1
time = 23
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame 0xfffffe0020f21690
vpanic() at vpanic+0x1e0/frame 0xfffffe0020f216f0
panic() at panic+0x43/frame 0xfffffe0020f21750
mtrash_ctor() at mtrash_ctor+0xed/frame 0xfffffe0020f21790
uma_zalloc_arg() at uma_zalloc_arg+0x1036/frame 0xfffffe0020f21840
malloc() at malloc+0xe1/frame 0xfffffe0020f218b0
sys_ioctl() at sys_ioctl+0x218/frame 0xfffffe0020f21980
amd64_syscall() at amd64_syscall+0x436/frame 0xfffffe0020f21ab0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe0020f21ab0
--- syscall (198, FreeBSD ELF64, nosys), rip = 0x4131ba, rsp = 0x7fffdfffdf38, rbp = 0x3 ---
KDB: enter: panic
[ thread pid 20400 tid 100552 ]
Stopped at      kdb_enter+0x6a: movq    $0,kdb_why

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/06/05 12:15 freebsd 54eb1c14c26e bfb4a51e console log report ci-freebsd-main
2019/06/04 17:33 freebsd 40124d2a0531 e41a20c5 console log report ci-freebsd-main
2019/05/05 22:50 freebsd 0d62ce242897 d28f4ce5 console log report ci-freebsd-main
* Struck through repros no longer work on HEAD.