Groups
Sign in
Groups
syzkaller-bugs
Conversations
About
Send feedback
Help
kernel panic: Fatal exception (3)
23 views
Skip to first unread message
syzbot
unread,
Oct 14, 2020, 4:12:26 PM
10/14/20
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to linux-...@vger.kernel.org, net...@vger.kernel.org, syzkall...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: c77fb07f Merge branch 'netlink-export-policy-on-validation..
git tree: net-next
console output:
https://syzkaller.appspot.com/x/log.txt?x=1722ff00500000
kernel config:
https://syzkaller.appspot.com/x/.config?x=fa2bf4058104211
dashboard link:
https://syzkaller.appspot.com/bug?extid=ec762a6342ad0d3c0d8f
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=1281459f900000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=175556f0500000
Bisection is inconclusive: the issue happens on the oldest tested release.
bisection log:
https://syzkaller.appspot.com/x/bisect.txt?x=11932b48500000
final oops:
https://syzkaller.appspot.com/x/report.txt?x=13932b48500000
console output:
https://syzkaller.appspot.com/x/log.txt?x=15932b48500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+ec762a...@syzkaller.appspotmail.com
FS: 0000000000000000(0000) GS:ffff8880ae500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004c9428 CR3: 0000000009e8d000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Kernel panic - not syncing: Fatal exception in interrupt
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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.
For information about bisection process see:
https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages