witness: reversal: fdlock inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d2e1daa0feb7 Cache CRLs in issuer cache
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=16cddb18580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=322a1e0d9e9448762d80

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cf2e3fcb224f/disk-d2e1daa0.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/71fb2cb86404/bsd-d2e1daa0.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c517274fdcb8/kernel-d2e1daa0.xz

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

witness: lock order reversal:
1st 0xfffffd806beb3858 fdlock (&newfdp->fd_fd.fd_lock)
2nd 0xfffffd806dd56dd8 inode (&ip->i_lock)
SYZFAIL: failed to recv rpc
fd=3 want=4 recv=0 n=-1 (errno 54: Connection reset by peer)


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