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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: feb640d47767 Remove unreachable check for orphaned process..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=108922e8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=c2ed3a30c5be3fa73173

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5ac17a2eb4ee/disk-feb640d4.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/f43b33b204cd/bsd-feb640d4.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cde613a9e399/kernel-feb640d4.xz

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

panic: kernel diagnostic assertion "d->bd_in_uiomove == 0" failed: file "/syzkaller/managers/main/kernel/sys/net/bpf.c", line 551
Starting stack trace...
panic(ffffffff830c1ea1) at panic+0x1ba sys/kern/subr_prf.c:229
__assert(ffffffff83075247,ffffffff830284df,227,ffffffff82ff5346) at __assert+0x29
bpfread(31700,ffff8000341fd360,0) at bpfread+0x79d sys/net/bpf.c:551
spec_read(ffff8000341fd150) at spec_read+0x14c sys/kern/spec_vnops.c:215
VOP_READ(fffffd8065834608,ffff8000341fd360,0,fffffd807f7d7478) at VOP_READ+0x102 sys/kern/vfs_vops.c:227

vn_read(fffffd806c215878,ffff8000341fd360,0) at vn_read+0x16d sys/kern/vfs_vnops.c:369
dofilereadv(ffff80002a513478,4,ffff8000341fd360,0,ffff8000341fd420) at dofilereadv+0x230 sys/kern/sys_generic.c:252
sys_readv(ffff80002a513478,ffff8000341fd4d0,ffff8000341fd420) at sys_readv+0xd8 sys/kern/sys_generic.c:199
syscall(ffff8000341fd4d0) at syscall+0x97e sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x28ed6515dc0, count: 247
End of stack trace.
syncing disks...set $lines = 0
set $maxwidth = 0
show panic
trace
show registers
show proc
ps
show all locks
show malloc
show all pools
machine ddbcpu 0
trace
machine ddbcpu 1
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.