panic: lock (sleep mutex) sctp-inp not locked @ /syzkaller/managers/i386/kernel/sys/netinet/sctp_pcb.c:LINE

0 views
Skip to first unread message

syzbot

unread,
Mar 15, 2024, 4:07:31 PMMar 15
to syzkaller-f...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d2a824c29d69 share/mk: Don't install only differing in cas..
git tree: freebsd-src
console output: https://syzkaller.appspot.com/x/log.txt?x=123b5185180000
dashboard link: https://syzkaller.appspot.com/bug?extid=0189280ed834f1650c42
userspace arch: i386

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+018928...@syzkaller.appspotmail.com

panic: lock (sleep mutex) sctp-inp not locked @ /syzkaller/managers/i386/kernel/sys/netinet/sctp_pcb.c:4433
cpuid = 0
time = 1710533219
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0xc6/frame 0xfffffe006a313450
kclient_loop: send disconnect: Broken pipe


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

unread,
Jun 16, 2024, 12:55:14 PM (5 days ago) Jun 16
to syzkaller-f...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages