SYZFAIL: coverage filter is full (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7f618044e74e Use PCB iterator for raw IP input deliver loop.
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=15914e30580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=623a173e5c593a428073

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/45b4254dea90/disk-7f618044.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/073a0dbb13ee/bsd-7f618044.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9f81a19d532d/kernel-7f618044.xz

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

SYZFAIL: coverage filter is full
pc=0x6e616c7f19 regions=[0xffffffffbfffffff 0x3fffffff 0x72657fffffff 0x7fffffff] alloc=37 (errno 35: Resource temporarily unavailable)


OpenBSD/amd64 (ci-openbsd-main-9.us-central1-b.c.syzkaller.internal) (tty00)

login: set $lines = 0
Password:
Login incorrect
login: show panic
Password:
Login incorrect
login: show registers
Password:
Login incorrect
login: ps
Password:
Login incorrect
show malloc
login: Password:
Login incorrect
machine ddbcpu 0
login: Password:
Login incorrect
machine ddbcpu 1
login: Password:
Login incorrect
login:


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