BUG: unable to handle kernel paging request in corrupted
24 views
Skip to first unread message
syzbot
Apr 15, 2018, 1:02:02 AM4/15/18
to linux-...@vger.kernel.org, syzkall...@googlegroups.com
Hello,
syzbot hit the following crash on upstream commit
c18bb396d3d261ebbb4efbc05129c5d354c541e4 (Tue Apr 10 00:04:10 2018 +0000)
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=bb6ed94ce15c5cd0be00
syzkaller reproducer:
https://syzkaller.appspot.com/x/repro.syz?id=6361086471176192
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=5146710238035968
Kernel config:
https://syzkaller.appspot.com/x/.config?id=-1223000601505858474
compiler: gcc (GCC) 8.0.1 20180301 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+bb6ed9...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
BUG: unable to handle kernel paging request at 0000000000005b63
PGD 1b67b2067 P4D 1b67b2067 PUD 1b67b3067 PMD 0
Oops: 0002 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 4510 Comm: syz-executor5 Not tainted 4.16.0+ #18
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
==================================================================
BUG: KASAN: out-of-bounds in vsnprintf+0x1a3b/0x1b40 lib/vsprintf.c:2315
Read of size 8 at addr -02 � ���e �6 � a by task syz-executor5/4510
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#2] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 4510 Comm: syz-executor5 Not tainted 4.16.0+ #18
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: b08e6540:die_lock+0x0/0x4
RSP: b08e6568:ffffffff81b2a8f1 EFLAGS: ffff8801b08e61e8 ORIG_RAX:
ffffed003611cc58
RAX: 1ffffffff10842bc RBX: ffff8801db021849 RCX: ffffffff874b04e3
RDX: 0000000000000000 RSI: ffffffff874b02f9 RDI: 0000000000000001
RBP: ffff8801b08e6568 R08: ffff8801c322e040 R09: ffffed003b6042bc
R10: ffffed003b6042bc R11: ffff8801db0215e3 R12: ffffffff884215e0
R13: ffffed003611cc58 R14: ffffffff898d54ec R15: ffff8801b08e6540
FS: 00007ff89fb7d700(0000) GS:ffff8801db000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000005b63 CR3: 00000001b67b1000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 <01> 00 00 00
02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
RIP: die_lock+0x0/0x4 RSP: ffffffff81b2a8f1
---[ end trace 4c7524c29b994875 ]---
---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
If you want to test a patch for this bug, please reply with:
#syz test: git://repo/address.git branch
and provide the patch inline or as an attachment.
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
syzbot hit the following crash on upstream commit
c18bb396d3d261ebbb4efbc05129c5d354c541e4 (Tue Apr 10 00:04:10 2018 +0000)
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=bb6ed94ce15c5cd0be00
syzkaller reproducer:
https://syzkaller.appspot.com/x/repro.syz?id=6361086471176192
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=5146710238035968
Kernel config:
https://syzkaller.appspot.com/x/.config?id=-1223000601505858474
compiler: gcc (GCC) 8.0.1 20180301 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+bb6ed9...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
BUG: unable to handle kernel paging request at 0000000000005b63
PGD 1b67b2067 P4D 1b67b2067 PUD 1b67b3067 PMD 0
Oops: 0002 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 4510 Comm: syz-executor5 Not tainted 4.16.0+ #18
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
==================================================================
BUG: KASAN: out-of-bounds in vsnprintf+0x1a3b/0x1b40 lib/vsprintf.c:2315
Read of size 8 at addr -02 � ���e �6 � a by task syz-executor5/4510
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#2] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 4510 Comm: syz-executor5 Not tainted 4.16.0+ #18
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: b08e6540:die_lock+0x0/0x4
RSP: b08e6568:ffffffff81b2a8f1 EFLAGS: ffff8801b08e61e8 ORIG_RAX:
ffffed003611cc58
RAX: 1ffffffff10842bc RBX: ffff8801db021849 RCX: ffffffff874b04e3
RDX: 0000000000000000 RSI: ffffffff874b02f9 RDI: 0000000000000001
RBP: ffff8801b08e6568 R08: ffff8801c322e040 R09: ffffed003b6042bc
R10: ffffed003b6042bc R11: ffff8801db0215e3 R12: ffffffff884215e0
R13: ffffed003611cc58 R14: ffffffff898d54ec R15: ffff8801b08e6540
FS: 00007ff89fb7d700(0000) GS:ffff8801db000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000005b63 CR3: 00000001b67b1000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 <01> 00 00 00
02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
RIP: die_lock+0x0/0x4 RSP: ffffffff81b2a8f1
---[ end trace 4c7524c29b994875 ]---
---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
If you want to test a patch for this bug, please reply with:
#syz test: git://repo/address.git branch
and provide the patch inline or as an attachment.
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
syzbot
Apr 16, 2018, 4:58:07 AM4/16/18
to Dmitry Vyukov, dvy...@google.com, syzkall...@googlegroups.com
> #syz upstream
Can't upstream, this is final destination.
> On Sun, Apr 15, 2018 at 7:02 AM, syzbot
> <syzbot+bb6ed9...@syzkaller.appspotmail.com> wrote:
>> Hello,
>> syzbot hit the following crash on upstream commit
>> c18bb396d3d261ebbb4efbc05129c5d354c541e4 (Tue Apr 10 00:04:10 2018 +0000)
>> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
>> syzbot dashboard link:
>> https://syzkaller.appspot.com/bug?extid=3Dbb6ed94ce15c5cd0be00
>> syzkaller reproducer:
>> https://syzkaller.appspot.com/x/repro.syz?id=3D6361086471176192
>> Raw console output:
>> https://syzkaller.appspot.com/x/log.txt?id=3D5146710238035968
>> Kernel config:
>> https://syzkaller.appspot.com/x/.config?id=3D-1223000601505858474
>> IPVS: ftp: loaded support on port[0] =3D 21
>> IPVS: ftp: loaded support on port[0] =3D 21
>> IPVS: ftp: loaded support on port[0] =3D 21
>> IPVS: ftp: loaded support on port[0] =3D 21
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> =BD6 =EF=BF=BD a by task syz-executor5/4510
>> kasan: CONFIG_KASAN_INLINE enabled
>> kasan: GPF could be caused by NULL-ptr deref or user memory access
>> general protection fault: 0000 [#2] SMP KASAN
>> Dumping ftrace buffer:
>> (ftrace buffer empty)
>> Modules linked in:
>> CPU: 0 PID: 4510 Comm: syz-executor5 Not tainted 4.16.0+ #18
>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
>> Google 01/01/2011
>> RIP: b08e6540:die_lock+0x0/0x4
>> RSP: b08e6568:ffffffff81b2a8f1 EFLAGS: ffff8801b08e61e8 ORIG_RAX:
>> ffffed003611cc58
>> RAX: 1ffffffff10842bc RBX: ffff8801db021849 RCX: ffffffff874b04e3
>> RDX: 0000000000000000 RSI: ffffffff874b02f9 RDI: 0000000000000001
>> RBP: ffff8801b08e6568 R08: ffff8801c322e040 R09: ffffed003b6042bc
>> R10: ffffed003b6042bc R11: ffff8801db0215e3 R12: ffffffff884215e0
>> R13: ffffed003611cc58 R14: ffffffff898d54ec R15: ffff8801b08e6540
>> FS: 00007ff89fb7d700(0000) GS:ffff8801db000000(0000)
>> knlGS:0000000000000=
> y.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "syzkaller-bugs" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to syzkaller-bug...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/syzkaller-bugs/001a1142766c7793080569dc=
> 017b%40google.com.
>> For more options, visit https://groups.google.com/d/optout.
Can't upstream, this is final destination.
> On Sun, Apr 15, 2018 at 7:02 AM, syzbot
> <syzbot+bb6ed9...@syzkaller.appspotmail.com> wrote:
>> Hello,
>> syzbot hit the following crash on upstream commit
>> c18bb396d3d261ebbb4efbc05129c5d354c541e4 (Tue Apr 10 00:04:10 2018 +0000)
>> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
>> syzbot dashboard link:
>> syzkaller reproducer:
>> https://syzkaller.appspot.com/x/repro.syz?id=3D6361086471176192
>> Raw console output:
>> https://syzkaller.appspot.com/x/log.txt?id=3D5146710238035968
>> Kernel config:
>> https://syzkaller.appspot.com/x/.config?id=3D-1223000601505858474
>> compiler: gcc (GCC) 8.0.1 20180301 (experimental)
>> IMPORTANT: if you fix the bug, please add the following tag to the
>> commit=
>> IMPORTANT: if you fix the bug, please add the following tag to the
> :
>> Reported-by: syzbot+bb6ed9...@syzkaller.appspotmail.com
>> It will help syzbot understand when the bug is fixed. See footer for
>> details.
>> If you forward the report, please keep this part and the footer.
>> IPVS: ftp: loaded support on port[0] =3D 21
>> Reported-by: syzbot+bb6ed9...@syzkaller.appspotmail.com
>> It will help syzbot understand when the bug is fixed. See footer for
>> details.
>> If you forward the report, please keep this part and the footer.
>> IPVS: ftp: loaded support on port[0] =3D 21
>> IPVS: ftp: loaded support on port[0] =3D 21
>> IPVS: ftp: loaded support on port[0] =3D 21
>> IPVS: ftp: loaded support on port[0] =3D 21
>> BUG: unable to handle kernel paging request at 0000000000005b63
>> PGD 1b67b2067 P4D 1b67b2067 PUD 1b67b3067 PMD 0
>> Oops: 0002 [#1] SMP KASAN
>> Dumping ftrace buffer:
>> (ftrace buffer empty)
>> Modules linked in:
>> CPU: 0 PID: 4510 Comm: syz-executor5 Not tainted 4.16.0+ #18
>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
>> Google 01/01/2011
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>> PGD 1b67b2067 P4D 1b67b2067 PUD 1b67b3067 PMD 0
>> Oops: 0002 [#1] SMP KASAN
>> Dumping ftrace buffer:
>> (ftrace buffer empty)
>> Modules linked in:
>> CPU: 0 PID: 4510 Comm: syz-executor5 Not tainted 4.16.0+ #18
>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
>> Google 01/01/2011
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> BUG: KASAN: out-of-bounds in vsnprintf+0x1a3b/0x1b40 lib/vsprintf.c:2315
>> Read of size 8 at addr -02 =EF=BF=BD =EF=BF=BD=EF=BF=BD=EF=BF=BDe =EF=BF=
> =BD6 =EF=BF=BD a by task syz-executor5/4510
>> kasan: CONFIG_KASAN_INLINE enabled
>> kasan: GPF could be caused by NULL-ptr deref or user memory access
>> general protection fault: 0000 [#2] SMP KASAN
>> Dumping ftrace buffer:
>> (ftrace buffer empty)
>> Modules linked in:
>> CPU: 0 PID: 4510 Comm: syz-executor5 Not tainted 4.16.0+ #18
>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
>> Google 01/01/2011
>> RIP: b08e6540:die_lock+0x0/0x4
>> RSP: b08e6568:ffffffff81b2a8f1 EFLAGS: ffff8801b08e61e8 ORIG_RAX:
>> ffffed003611cc58
>> RAX: 1ffffffff10842bc RBX: ffff8801db021849 RCX: ffffffff874b04e3
>> RDX: 0000000000000000 RSI: ffffffff874b02f9 RDI: 0000000000000001
>> RBP: ffff8801b08e6568 R08: ffff8801c322e040 R09: ffffed003b6042bc
>> R10: ffffed003b6042bc R11: ffff8801db0215e3 R12: ffffffff884215e0
>> R13: ffffed003611cc58 R14: ffffffff898d54ec R15: ffff8801b08e6540
>> FS: 00007ff89fb7d700(0000) GS:ffff8801db000000(0000)
> 000
>> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> CR2: 0000000000005b63 CR3: 00000001b67b1000 CR4: 00000000001426f0
>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
>> Call Trace:
>> Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 0=
>> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> CR2: 0000000000005b63 CR3: 00000001b67b1000 CR4: 00000000001426f0
>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
>> Call Trace:
>> Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 <01> 00 00
>> 00=
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 <01> 00 00
> 02
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> RIP: die_lock+0x0/0x4 RSP: ffffffff81b2a8f1
>> ---[ end trace 4c7524c29b994875 ]---
>> ---
>> This bug is generated by a dumb bot. It may contain errors.
>> See https://goo.gl/tpsmEJ for details.
>> Direct all questions to syzk...@googlegroups.com.
>> syzbot will keep track of this bug report.
>> If you forgot to add the Reported-by tag, once the fix for this bug is
>> merged
>> into any tree, please reply to this email with:
>> #syz fix: exact-commit-title
>> If you want to test a patch for this bug, please reply with:
>> #syz test: git://repo/address.git branch
>> and provide the patch inline or as an attachment.
>> To mark this as a duplicate of another syzbot report, please reply with:
>> #syz dup: exact-subject-of-another-report
>> If it's a one-off invalid bug report, please reply with:
>> #syz invalid
>> Note: if the crash happens again, it will cause creation of a new bug
>> report.
>> Note: all commands must start from beginning of the line in the email
>> bod=
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> RIP: die_lock+0x0/0x4 RSP: ffffffff81b2a8f1
>> ---[ end trace 4c7524c29b994875 ]---
>> ---
>> This bug is generated by a dumb bot. It may contain errors.
>> See https://goo.gl/tpsmEJ for details.
>> Direct all questions to syzk...@googlegroups.com.
>> syzbot will keep track of this bug report.
>> If you forgot to add the Reported-by tag, once the fix for this bug is
>> merged
>> into any tree, please reply to this email with:
>> #syz fix: exact-commit-title
>> If you want to test a patch for this bug, please reply with:
>> #syz test: git://repo/address.git branch
>> and provide the patch inline or as an attachment.
>> To mark this as a duplicate of another syzbot report, please reply with:
>> #syz dup: exact-subject-of-another-report
>> If it's a one-off invalid bug report, please reply with:
>> #syz invalid
>> Note: if the crash happens again, it will cause creation of a new bug
>> report.
>> Note: all commands must start from beginning of the line in the email
> y.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "syzkaller-bugs" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to syzkaller-bug...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/syzkaller-bugs/001a1142766c7793080569dc=
> 017b%40google.com.
>> For more options, visit https://groups.google.com/d/optout.
Dmitry Vyukov
Apr 16, 2018, 5:11:08 AM4/16/18
to syzbot, Paolo Bonzini, Radim Krčmář, KVM list, LKML, syzkaller-bugs
> Hello,
>
> syzbot hit the following crash on upstream commit
> c18bb396d3d261ebbb4efbc05129c5d354c541e4 (Tue Apr 10 00:04:10 2018 +0000)
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
> syzbot dashboard link:
> https://syzkaller.appspot.com/bug?extid=bb6ed94ce15c5cd0be00
>
> syzkaller reproducer:
> https://syzkaller.appspot.com/x/repro.syz?id=6361086471176192
> Raw console output:
> https://syzkaller.appspot.com/x/log.txt?id=5146710238035968
> Kernel config:
> https://syzkaller.appspot.com/x/.config?id=-1223000601505858474
> compiler: gcc (GCC) 8.0.1 20180301 (experimental)
Looking at the reproducer, it seems that KVM somehow badly corrupts
>
> syzbot hit the following crash on upstream commit
> c18bb396d3d261ebbb4efbc05129c5d354c541e4 (Tue Apr 10 00:04:10 2018 +0000)
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
> syzbot dashboard link:
> https://syzkaller.appspot.com/bug?extid=bb6ed94ce15c5cd0be00
>
> syzkaller reproducer:
> https://syzkaller.appspot.com/x/repro.syz?id=6361086471176192
> Raw console output:
> https://syzkaller.appspot.com/x/log.txt?id=5146710238035968
> Kernel config:
> https://syzkaller.appspot.com/x/.config?id=-1223000601505858474
> compiler: gcc (GCC) 8.0.1 20180301 (experimental)
memory. +kvm maintainers.
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-bugs/001a1142766c7793080569dc017b%40google.com.
> You received this message because you are subscribed to the Google Groups
> "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit
syzbot
Jun 24, 2018, 8:36:03 AM6/24/18
to dvy...@google.com, k...@vger.kernel.org, linux-...@vger.kernel.org, pbon...@redhat.com, rkr...@redhat.com, syzkall...@googlegroups.com
syzbot has found a reproducer for the following crash on:
HEAD commit: 77072ca59fdd Merge tag 'for-linus-20180623' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12abe040400000
kernel config: https://syzkaller.appspot.com/x/.config?x=befbcd7305e41bb0
dashboard link: https://syzkaller.appspot.com/bug?extid=bb6ed94ce15c5cd0be00
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=1762ec7f800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1556ee38400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+bb6ed9...@syzkaller.appspotmail.com
8021q: adding VLAN 0 to HW filter on device bond0
IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
8021q: adding VLAN 0 to HW filter on device team0
BUG: unable to handle kernel paging request at ffffc90001e1ee68
PGD 1da947067 P4D 1da947067 PUD 1da948067 PMD 1ad8b7067 PTE 0
HEAD commit: 77072ca59fdd Merge tag 'for-linus-20180623' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12abe040400000
kernel config: https://syzkaller.appspot.com/x/.config?x=befbcd7305e41bb0
dashboard link: https://syzkaller.appspot.com/bug?extid=bb6ed94ce15c5cd0be00
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=1762ec7f800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1556ee38400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+bb6ed9...@syzkaller.appspotmail.com
IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
8021q: adding VLAN 0 to HW filter on device team0
BUG: unable to handle kernel paging request at ffffc90001e1ee68
PGD 1da947067 P4D 1da947067 PUD 1da948067 PMD 1ad8b7067 PTE 0
Eric Biggers
Jun 11, 2019, 2:50:01 AM6/11/19
to syzbot, syzkall...@googlegroups.com
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/00000000000007b7ba056f628249%40google.com.
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bug...@googlegroups.com.
This last occurred months ago and there seem to be 3 different bugs mixed into
the syzbot report, so I think it's best to just invalidate this mess and start
from scratch...
#syz invalid
Reply all
Reply to author
Forward
0 new messages