syzbot
corrupted report
Status:
closed as dup on 2019/08/27 18:20
Reported-by: syzbot+80f0456bb602e8a7030d@syzkaller.appspotmail.com
First crash: 2536d, last: 2523d
Sample crash report:
panic: malloc: allocation too large, type = 2, size = 18446744073709550976
Stopped at db_enter+0x18: addq $0x8,%rsp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*387994 45685 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(ffff800015946680) at vm_get_info+0x9a
VOP_IOCTL(fffffd80361865b0,c0185603,ffff800015946680,1,fffffd803f7c68a0,ffff800014f35160) at VOP_IOCTL+0x88 sys/kern/vfs_vops.c:291
vn_ioctl(fffffd802f8e8108,c0185603,ffff800015946680,ffff800014f35160) at vn_ioctl+0xb7 sys/kern/vfs_vnops.c:524
sys_ioctl(ffff800014f35160,ffff800015946798,ffff8000159467e0) at sys_ioctl+0x5b9
syscall(ffff800015946860) at syscall+0x507 sys/arch/amd64/amd64/trap.c:555
Xsyscall(6,0,ffffffffffffff53,0,3,1a2a989c1b0) at Xsyscall+0x128
end of kernel
end trace frame: 0x1a5a4399350, 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.
ddb>
ddb> set $lines = 0
ddb> serialport: VM disconnected.
* Struck through repros no longer work on HEAD.