panic: Assertion in_epoch(net_epoch_preempt) failed at /syzkaller/managers/i386/kernel/sys/net/if.c:LINE
1 view
Skip to first unread message
syzbot
Oct 8, 2019, 1:24:07 PM10/8/19
to syzkaller-f...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 1c64917f Quickly plug another regression from r353292. Aga..
git tree: freebsd
console output: https://syzkaller.appspot.com/x/log.txt?x=17d9108b600000
dashboard link: https://syzkaller.appspot.com/bug?extid=ee3d713a166847eefd50
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+ee3d71...@syzkaller.appspotmail.com
login: panic: Assertion in_epoch(net_epoch_preempt) failed at
/syzkaller/managers/i386/kernel/sys/net/if.c:3827
cpuid = 0
time = 1570555374
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame
0xfffffe002426d5b0
vpanic() at vpanic+0x1e0/frame 0xfffffe002426d610
panic() at panic+0x43/frame 0xfffffe002426d670
if_setlladdr() at if_setlladdr+0x34c/frame 0xfffffe002426d6e0
ifhwioctl() at ifhwioctl+0x9e0/frame 0xfffffe002426d770
ifioctl() at ifioctl+0x4c2/frame 0xfffffe002426d840
kern_ioctl() at kern_ioctl+0x465/frame 0xfffffe002426d8b0
sys_ioctl() at sys_ioctl+0x267/frame 0xfffffe002426d980
amd64_syscall() at amd64_syscall+0x477/frame 0xfffffe002426dab0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe002426dab0
--- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x8004882ca, rsp =
0x7fffffffe428, rbp = 0x7fffffffe470 ---
KDB: enter: panic
[ thread pid 769 tid 100087 ]
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 found the following crash on:
HEAD commit: 1c64917f Quickly plug another regression from r353292. Aga..
git tree: freebsd
console output: https://syzkaller.appspot.com/x/log.txt?x=17d9108b600000
dashboard link: https://syzkaller.appspot.com/bug?extid=ee3d713a166847eefd50
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+ee3d71...@syzkaller.appspotmail.com
login: panic: Assertion in_epoch(net_epoch_preempt) failed at
/syzkaller/managers/i386/kernel/sys/net/if.c:3827
cpuid = 0
time = 1570555374
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame
0xfffffe002426d5b0
vpanic() at vpanic+0x1e0/frame 0xfffffe002426d610
panic() at panic+0x43/frame 0xfffffe002426d670
if_setlladdr() at if_setlladdr+0x34c/frame 0xfffffe002426d6e0
ifhwioctl() at ifhwioctl+0x9e0/frame 0xfffffe002426d770
ifioctl() at ifioctl+0x4c2/frame 0xfffffe002426d840
kern_ioctl() at kern_ioctl+0x465/frame 0xfffffe002426d8b0
sys_ioctl() at sys_ioctl+0x267/frame 0xfffffe002426d980
amd64_syscall() at amd64_syscall+0x477/frame 0xfffffe002426dab0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe002426dab0
--- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x8004882ca, rsp =
0x7fffffffe428, rbp = 0x7fffffffe470 ---
KDB: enter: panic
[ thread pid 769 tid 100087 ]
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.
Mark Johnston
Oct 8, 2019, 1:27:35 PM10/8/19
to gle...@freebsd.org, syzkaller-f...@googlegroups.com
Could you take a look at this?
syzbot
Dec 8, 2019, 6:01:05 AM12/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.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages