panic: mallocic: koraeio nd tagnosric,asypr = 2 !_ikzeer n=e l_l4ADDR(3)7" ADDR

3 views
Skip to first unread message

syzbot

unread,
Sep 6, 2019, 3:14:06 AM9/6/19
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 87bcbcf5 sync
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=13ad503e600000
kernel config: https://syzkaller.appspot.com/x/.config?x=26ca0a9c07f16a3a
dashboard link: https://syzkaller.appspot.com/bug?extid=34e36c1ec7973c5547a5

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

login: panic: mallocic: koraeio nd tagnosric,asypr = 2 !_ikzeer n=e
l_l4467440d(3)7" 5f5a65e
:
Stopped at db_enter+0x18: addq $0x8,%rsp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*144283 22042 0 0 0x4000000 0 syz-executor.1
222540 31259 0 0 0x4000000 1 syz-executor.0
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(fffffffffffffc40,2,a) at malloc+0x9c9 sys/kern/kern_malloc.c:344
vm_get_info(ffff800021b77590) at vm_get_info+0x9d
VOP_IOCTL(fffffd806e0c7a90,c0185603,ffff800021b77590,1,fffffd807f7c6960,ffff800020ab0780)
at
VOP_IOCTL+0x88 sys/kern/vfs_vops.c:291
vn_ioctl(fffffd807b7ecee8,c0185603,ffff800021b77590,ffff800020ab0780) at
vn_ioctl+0xb7 sys/kern/vfs_vnops.c:524
sys_ioctl(ffff800020ab0780,ffff800021b776a8,ffff800021b776f0) at
sys_ioctl+0x5b9
syscall(ffff800021b77770) at syscall+0x4a4 mi_syscall
sys/sys/syscall_mi.h:92 [inline]
syscall(ffff800021b77770) at syscall+0x4a4 sys/arch/amd64/amd64/trap.c:555
Xsyscall(6,0,ffffffffffffff53,0,3,8220338f0e0) at Xsyscall+0x128
end of kernel
end trace frame: 0x82407ccf1c0, 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.


---
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.

Anton Lindqvist

unread,
Sep 6, 2019, 3:52:34 AM9/6/19
to syzbot, syzkaller-o...@googlegroups.com
#syz dup: panic: malloc: allocation too large, type = 2, size = ADDR (2)
Reply all
Reply to author
Forward
0 new messages