panic: Assertion in_epoch(net_epoch_preempt) failed at /syzkaller/managers/i386/kernel/sys/netinet/in_mcast.c:LINE

1 view
Skip to first unread message

syzbot

unread,
Oct 9, 2019, 8:08:07 AM10/9/19
to syzkaller-f...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 6bf933c4 Revert changes to rip6_bind() from r353292. This..
git tree: freebsd
console output: https://syzkaller.appspot.com/x/log.txt?x=13a52ebf600000
dashboard link: https://syzkaller.appspot.com/bug?extid=b6c0d8741696e6f82cac
userspace arch: i386

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

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

panic: Assertion in_epoch(net_epoch_preempt) failed at
/syzkaller/managers/i386/kernel/sys/netinet/in_mcast.c:1319
cpuid = 1
time = 1570622867
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame
0xfffffe0022baf4b0
vpanic() at vpanic+0x1e0/frame 0xfffffe0022baf510
panic() at panic+0x43/frame 0xfffffe0022baf570
in_leavegroup_locked() at in_leavegroup_locked+0x215/frame
0xfffffe0022baf5d0
inp_setmoptions() at inp_setmoptions+0x1290/frame 0xfffffe0022baf7a0
ip_ctloutput() at ip_ctloutput+0x823/frame 0xfffffe0022baf800
rip_ctloutput() at rip_ctloutput+0x2c9/frame 0xfffffe0022baf840
sosetopt() at sosetopt+0x101/frame 0xfffffe0022baf8c0
kern_setsockopt() at kern_setsockopt+0x14f/frame 0xfffffe0022baf940
sys_setsockopt() at sys_setsockopt+0x33/frame 0xfffffe0022baf970
ia32_syscall() at ia32_syscall+0x46a/frame 0xfffffe0022bafab0
int0x80_syscall_common() at int0x80_syscall_common+0x9c/frame 0x81431ca
KDB: enter: panic
[ thread pid 31425 tid 100643 ]
Stopped at kdb_enter+0x6a: movq $0,kdb_why


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Dec 8, 2019, 1:07:06 PM12/8/19
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