SYZFAIL: too many calls in output

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fb05f761ac0b siftr: remove the shutdown_pre_sync event han..
git tree: freebsd-src
console output: https://syzkaller.appspot.com/x/log.txt?x=10e10195980000
dashboard link: https://syzkaller.appspot.com/bug?extid=9281f3c5191b65a4dde2

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

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

SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: No error: 0)
SYZFAIL: repeatedly failed to execute the program
proc=2 req=1000 state=3 status=67 (errno 9: Bad file descriptor)


FreeBSD/amd64 (ci-freebsd-main-0.c.syzkaller.internal) (ttyu0)

login: set $lines = 0
Password:
Login incorrect
login: show registers
Password:
Login incorrect
login: ps
Jul 20 02:31:44 ci-freebsd-main-0 syslogd: last message repeated 1 times
Jul 20 02:31:45 ci-freebsd-main-0 login[748]: 2 LOGIN FAILURES ON ttyu0
Password:
Login incorrect
login: show malloc
Password:
Login incorrect


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