assert "d->bd_in_uiomove == NUM" failed in bpf.c (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 31aef2a8f397 Convert the last few K&R function definitions..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1780688c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=53cde92f182d7250ccd7

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/34419d9130d0/disk-31aef2a8.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/40a1d14a2be4/bsd-31aef2a8.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/40165165f1c7/kernel-31aef2a8.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+53cde9...@syzkaller.appspotmail.com

panic: kernel diagnostic assertion "d->bd_in_uiomove == 0" failed: file "/syzkaller/managers/main/kernel/sys/net/bpf.c", line 550
Starting stack trace...
panic(ffffffff834316bf) at panic+0x1ba sys/kern/subr_prf.c:229
__assert(ffffffff833e1ca0,ffffffff8339326d,226,ffffffff8335a8c4) at __assert+0x29 sys/kern/subr_prf.c:-1
bpfread(41700,ffff80003c997a30,0) at bpfread+0x79d sys/net/bpf.c:550
spec_read(ffff80003c997820) at spec_read+0x14c sys/kern/spec_vnops.c:215
VOP_READ(fffffd806e6ac7e8,ffff80003c997a30,0,fffffd8007bfb7b8) at VOP_READ+0x102 sys/kern/vfs_vops.c:227
vn_read(fffffd8061ba71e8,ffff80003c997a30,0) at vn_read+0x16d sys/kern/vfs_vnops.c:369
dofilereadv(ffff80002a7e2f78,7,ffff80003c997a30,0,ffff80003c997af0) at dofilereadv+0x230 sys/kern/sys_generic.c:252
sys_readv(ffff80002a7e2f78,ffff80003c997ba0,ffff80003c997af0) at sys_readv+0xd8 sys/kern/sys_generic.c:199
syscall(ffff80003c997ba0) at syscall+0x97e mi_syscall sys/sys/syscall_mi.h:-1 [inline]
syscall(ffff80003c997ba0) at syscall+0x97e sys/arch/amd64/amd64/trap.c:637
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x2f8874a3f10, count: 247
End of stack trace.


---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.