From: syzbot <syzbot+bb6ed94ce15c5cd0be00@syzkaller.appspotmail.com>
To: dvyukov@google.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, pbonzini@redhat.com,
rkrcmar@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: BUG: unable to handle kernel paging request in corrupted
Date: Sun, 24 Jun 2018 05:36:02 -0700 [thread overview]
Message-ID: <00000000000007b7ba056f628249@google.com> (raw)
In-Reply-To: <001a1142766c7793080569dc017b@google.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+bb6ed94ce15c5cd0be00@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
prev parent reply other threads:[~2018-06-24 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a1142766c7793080569dc017b@google.com>
2018-04-16 9:10 ` BUG: unable to handle kernel paging request in corrupted Dmitry Vyukov
2018-06-24 12:36 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000007b7ba056f628249@google.com \
--to=syzbot+bb6ed94ce15c5cd0be00@syzkaller.appspotmail.com \
--cc=dvyukov@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox