witness: reversal: sbufsnd inode (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3411e7e2a484 Revert SMR protection of rt_gwroute.
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=13c397df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=1be12bd88b5b1508ddd5

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/61e819b81e49/disk-3411e7e2.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/40f21e74da44/bsd-3411e7e2.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/efb45e94d194/kernel-3411e7e2.xz

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

witness: lock order reversal:
1st 0xffff800010fe01d0 sbufsnd (&so->so_snd.sb_lock)
2nd 0xfffffd8079165ee0 inode (&ip->i_lock)


OpenBSD/amd64 (Amnesiac) (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


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