syzbot


panic: malloc: allocation too large, type = 2, sizep a=n 1i8c4: 46ke74rn4e0l7 37di0a9g55no0s9t7i6c

Status: closed as dup on 2019/09/02 21:11
Reported-by: syzbot+6177393c9cd1f38553c2@syzkaller.appspotmail.com
First crash: 1937d, last: 1937d
Duplicate of
Title Repro Cause bisect Fix bisect Count Last Reported
panic: malloc: allocation too large, type = 2, size = ADDR (2) C 16842 1928d 1946d

Sample crash report:
panic: malloc: allocation too large, type = 2, sizep a=n 1i8c4: 46ke74rn4e0l7 37di0a9g55no0s9t7i6c
 
a
sStopped at      db_enter+0x18:  addq    $0x8,%rsp
    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
 220507  65363      0           0  0x4000000    1  syz-executor.0
* 25020  73363      0           0  0x4000000    0  syz-executor.1
db_enter() at db_enter+0x18 sys/arch/amd64/amd64/db_interface.c:398
panic() at panic+0x15c sys/kern/subr_prf.c:207
malloc(fffffffffffffd80,2,a) at malloc+0x9c9 sys/kern/kern_malloc.c:344
vm_get_info(ffff800022bad610) at vm_get_info+0x9d
VOP_IOCTL(fffffd806e1fdb60,c0185603,ffff800022bad610,ca,fffffd807f7c6960,ffff800020ab0290) at VOP_IOCTL+0x88 sys/kern/vfs_vops.c:291
vn_ioctl(fffffd806735e998,c0185603,ffff800022bad610,ffff800020ab0290) at vn_ioctl+0xb7 sys/kern/vfs_vnops.c:524
sys_ioctl(ffff800020ab0290,ffff800022bad728,ffff800022bad770) at sys_ioctl+0x5b9
syscall(ffff800022bad7f0) at syscall+0x4a4 mi_syscall sys/sys/syscall_mi.h:92 [inline]
syscall(ffff800022bad7f0) at syscall+0x4a4 sys/arch/amd64/amd64/trap.c:555
Xsyscall(6,0,ffffffffffffff53,0,3,506a9ad90e0) at Xsyscall+0x128
end of kernel
end trace frame: 0x508ef9b7750, count: 6
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports.  Insufficient info makes it difficult to find and fix bugs.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/09/02 09:29 openbsd 0c2868d616e1 db7c31ca .config console log report ci-openbsd-multicore
* Struck through repros no longer work on HEAD.