Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Tested-by: syzbot <[email protected]>
Once the fix is committed, please reply to this email with:
#syz fix: exact-commit-title
Tested on commit 95bc2c5eda50e60089563544638f68e26973521d
git://git.kernel.org/pub/scm/virt/kvm/kvm.git/next
compiler: gcc (GCC) 7.1.1 20170620
Patch is attached.
Kernel config is attached.
---
There is no WARRANTY for the result, to the extent permitted by applicable
law.
Except when otherwise stated in writing syzbot provides the result "AS IS"
without warranty of any kind, either expressed or implied, but not limited
to,
the implied warranties of merchantability and fittness for a particular
purpose.
The entire risk as to the quality of the result is with you. Should the
result
prove defective, you assume the cost of all necessary servicing, repair or
correction.
2017-11-20 20:06 GMT+08:00 Dmitry Vyukov <[email protected]>:
> On Mon, Nov 20, 2017 at 10:23 AM, Dmitry Vyukov <[email protected]> wrote:
>> On Mon, Nov 20, 2017 at 10:19 AM, Wanpeng Li <[email protected]> wrote:
>>> Hi Dmitry,
>>> 2017-11-20 12:09 GMT+08:00 Wanpeng Li <[email protected]>:
>>>> 2017-11-18 4:22 GMT+08:00 syzbot
>>>> <bot+d9fbc5c299aa8a95ac07572b4f6e191c0f4efff6@syzkaller.appspotmail.com>:
>>>>> Hello,
>>>>>
>>>>> syzbot has tested the proposed patch but the reproducer still triggered
>>>>> crash:
>>>>> WARNING in kvm_arch_vcpu_ioctl_run
>>>>>
>>>>> VMExit: intr_info=00000000 errcode=00000000 ilen=00000000
>>>>> reason=80000021 qualification=0000000000000000
>>>>> IDTVectoring: info=00000000 errcode=00000000
>>>>> TSC Offset = 0xffffffeeb46bc6ac
>>>>> EPT pointer = 0x00000001ce37601e
>>>>> WARNING: CPU: 0 PID: 3023 at arch/x86/kvm/x86.c:7293
>>>>> kvm_arch_vcpu_ioctl_run+0x213/0x5d20
>>>>> Kernel panic - not syncing: panic_on_warn set ...
>>>>>
>>>>> CPU: 0 PID: 3023 Comm: syz-executor4 Not tainted 4.14.0-next-20171117+ #9
>>>>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
>>>>> Google 01/01/2011
>>>>> Call Trace:
>>>>> dump_stack+0x173/0x237
>>>>> panic+0x1e4/0x41c
>>>>> __warn+0x1d9/0x1f0
>>>>> report_bug+0x20a/0x2d0
>>>>> fixup_bug.part.10+0x32/0x80
>>>>> do_error_trap+0x29c/0x370
>>>>> invalid_op+0x18/0x20
>>>>> RIP: 0010:kvm_arch_vcpu_ioctl_run+0x213/0x5d20
>>>>> RSP: 0018:ffff8801ce197680 EFLAGS: 00010293
>>>>> RAX: ffff8801ce588440 RBX: ffff8801d5b8f000 RCX: ffffffff810d4003
>>>>> RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8801ce0e02b8
>>>>> RBP: ffff8801ce197a50 R08: 0000000000000001 R09: 0000000000000001
>>>>> R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
>>>>> R13: ffff8801ce0e0168 R14: ffff8801cec10980 R15: ffff8801ce0e0080
>>>>> kvm_vcpu_ioctl+0x619/0xf80
>>>>> do_vfs_ioctl+0x18b/0x13e0
>>>>> SyS_ioctl+0x7e/0xb0
>>>>> entry_SYSCALL_64_fastpath+0x1f/0x96
>>>>> RIP: 0033:0x452879
>>>>> RSP: 002b:00007f4bc97fdbe8 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
>>>>> RAX: ffffffffffffffda RBX: 0000000000000082 RCX: 0000000000452879
>>>>> RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000004
>>>>> RBP: 00007ffce1993510 R08: 0000000000000000 R09: 0000000000000000
>>>>> R10: 0000000000000000 R11: 0000000000000212 R12: 0000000000000000
>>>>> R13: 00007ffce199348f R14: 00007f4bc97fe9c0 R15: 0000000000000006
>>>>> Dumping ftrace buffer:
>>>>> (ftrace buffer empty)
>>>>> Kernel Offset: disabled
>>>>> Rebooting in 86400 seconds..
>>>>
>>>> I will have a look.
>>>
>>> Please have a try. https://lkml.org/lkml/2017/11/20/118
>>
>> Hi Wanpeng,
>>
>> There is shiny new feature being rolled for syzbot, see "#syz test" here:
>>
>> https://github.com/google/syzkaller/blob/master/docs/syzbot.md#communication-with-syzbot
>>
>> Please have a try ;)
>
>
> Bringing some of offline discussion online. We are unable to test
> patches for hundreds of bugs reported across branches/releases/OSes
> and want to automate most of the process.
> Let's give it a try still:
>
> #syz test: git://git.kernel.org/pub/scm/virt/kvm/kvm.git next
The patch fixes the bug which the repro.c triggers, so I'm fine with
the result and thanks for your report. :)
Regards,
Wanpeng Li
From 1584586728727223251@xxx Mon Nov 20 12:07:45 +0000 2017
X-GM-THRID: 1582895480167067631
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread
On Mon, Nov 20, 2017 at 10:23 AM, Dmitry Vyukov <[email protected]> wrote:
> On Mon, Nov 20, 2017 at 10:19 AM, Wanpeng Li <[email protected]> wrote:
>> Hi Dmitry,
>> 2017-11-20 12:09 GMT+08:00 Wanpeng Li <[email protected]>:
>>> 2017-11-18 4:22 GMT+08:00 syzbot
>>> <bot+d9fbc5c299aa8a95ac07572b4f6e191c0f4efff6@syzkaller.appspotmail.com>:
>>>> Hello,
>>>>
>>>> syzbot has tested the proposed patch but the reproducer still triggered
>>>> crash:
>>>> WARNING in kvm_arch_vcpu_ioctl_run
>>>>
>>>> VMExit: intr_info=00000000 errcode=00000000 ilen=00000000
>>>> reason=80000021 qualification=0000000000000000
>>>> IDTVectoring: info=00000000 errcode=00000000
>>>> TSC Offset = 0xffffffeeb46bc6ac
>>>> EPT pointer = 0x00000001ce37601e
>>>> WARNING: CPU: 0 PID: 3023 at arch/x86/kvm/x86.c:7293
>>>> kvm_arch_vcpu_ioctl_run+0x213/0x5d20
>>>> Kernel panic - not syncing: panic_on_warn set ...
>>>>
>>>> CPU: 0 PID: 3023 Comm: syz-executor4 Not tainted 4.14.0-next-20171117+ #9
>>>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
>>>> Google 01/01/2011
>>>> Call Trace:
>>>> dump_stack+0x173/0x237
>>>> panic+0x1e4/0x41c
>>>> __warn+0x1d9/0x1f0
>>>> report_bug+0x20a/0x2d0
>>>> fixup_bug.part.10+0x32/0x80
>>>> do_error_trap+0x29c/0x370
>>>> invalid_op+0x18/0x20
>>>> RIP: 0010:kvm_arch_vcpu_ioctl_run+0x213/0x5d20
>>>> RSP: 0018:ffff8801ce197680 EFLAGS: 00010293
>>>> RAX: ffff8801ce588440 RBX: ffff8801d5b8f000 RCX: ffffffff810d4003
>>>> RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8801ce0e02b8
>>>> RBP: ffff8801ce197a50 R08: 0000000000000001 R09: 0000000000000001
>>>> R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
>>>> R13: ffff8801ce0e0168 R14: ffff8801cec10980 R15: ffff8801ce0e0080
>>>> kvm_vcpu_ioctl+0x619/0xf80
>>>> do_vfs_ioctl+0x18b/0x13e0
>>>> SyS_ioctl+0x7e/0xb0
>>>> entry_SYSCALL_64_fastpath+0x1f/0x96
>>>> RIP: 0033:0x452879
>>>> RSP: 002b:00007f4bc97fdbe8 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
>>>> RAX: ffffffffffffffda RBX: 0000000000000082 RCX: 0000000000452879
>>>> RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000004
>>>> RBP: 00007ffce1993510 R08: 0000000000000000 R09: 0000000000000000
>>>> R10: 0000000000000000 R11: 0000000000000212 R12: 0000000000000000
>>>> R13: 00007ffce199348f R14: 00007f4bc97fe9c0 R15: 0000000000000006
>>>> Dumping ftrace buffer:
>>>> (ftrace buffer empty)
>>>> Kernel Offset: disabled
>>>> Rebooting in 86400 seconds..
>>>
>>> I will have a look.
>>
>> Please have a try. https://lkml.org/lkml/2017/11/20/118
>
> Hi Wanpeng,
>
> There is shiny new feature being rolled for syzbot, see "#syz test" here:
>
> https://github.com/google/syzkaller/blob/master/docs/syzbot.md#communication-with-syzbot
>
> Please have a try ;)
Bringing some of offline discussion online. We are unable to test
patches for hundreds of bugs reported across branches/releases/OSes
and want to automate most of the process.
Let's give it a try still:
#syz test: git://git.kernel.org/pub/scm/virt/kvm/kvm.git next
On Mon, Nov 20, 2017 at 10:19 AM, Wanpeng Li <[email protected]> wrote:
> Hi Dmitry,
> 2017-11-20 12:09 GMT+08:00 Wanpeng Li <[email protected]>:
>> 2017-11-18 4:22 GMT+08:00 syzbot
>> <bot+d9fbc5c299aa8a95ac07572b4f6e191c0f4efff6@syzkaller.appspotmail.com>:
>>> Hello,
>>>
>>> syzbot has tested the proposed patch but the reproducer still triggered
>>> crash:
>>> WARNING in kvm_arch_vcpu_ioctl_run
>>>
>>> VMExit: intr_info=00000000 errcode=00000000 ilen=00000000
>>> reason=80000021 qualification=0000000000000000
>>> IDTVectoring: info=00000000 errcode=00000000
>>> TSC Offset = 0xffffffeeb46bc6ac
>>> EPT pointer = 0x00000001ce37601e
>>> WARNING: CPU: 0 PID: 3023 at arch/x86/kvm/x86.c:7293
>>> kvm_arch_vcpu_ioctl_run+0x213/0x5d20
>>> Kernel panic - not syncing: panic_on_warn set ...
>>>
>>> CPU: 0 PID: 3023 Comm: syz-executor4 Not tainted 4.14.0-next-20171117+ #9
>>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
>>> Google 01/01/2011
>>> Call Trace:
>>> dump_stack+0x173/0x237
>>> panic+0x1e4/0x41c
>>> __warn+0x1d9/0x1f0
>>> report_bug+0x20a/0x2d0
>>> fixup_bug.part.10+0x32/0x80
>>> do_error_trap+0x29c/0x370
>>> invalid_op+0x18/0x20
>>> RIP: 0010:kvm_arch_vcpu_ioctl_run+0x213/0x5d20
>>> RSP: 0018:ffff8801ce197680 EFLAGS: 00010293
>>> RAX: ffff8801ce588440 RBX: ffff8801d5b8f000 RCX: ffffffff810d4003
>>> RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8801ce0e02b8
>>> RBP: ffff8801ce197a50 R08: 0000000000000001 R09: 0000000000000001
>>> R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
>>> R13: ffff8801ce0e0168 R14: ffff8801cec10980 R15: ffff8801ce0e0080
>>> kvm_vcpu_ioctl+0x619/0xf80
>>> do_vfs_ioctl+0x18b/0x13e0
>>> SyS_ioctl+0x7e/0xb0
>>> entry_SYSCALL_64_fastpath+0x1f/0x96
>>> RIP: 0033:0x452879
>>> RSP: 002b:00007f4bc97fdbe8 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
>>> RAX: ffffffffffffffda RBX: 0000000000000082 RCX: 0000000000452879
>>> RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000004
>>> RBP: 00007ffce1993510 R08: 0000000000000000 R09: 0000000000000000
>>> R10: 0000000000000000 R11: 0000000000000212 R12: 0000000000000000
>>> R13: 00007ffce199348f R14: 00007f4bc97fe9c0 R15: 0000000000000006
>>> Dumping ftrace buffer:
>>> (ftrace buffer empty)
>>> Kernel Offset: disabled
>>> Rebooting in 86400 seconds..
>>
>> I will have a look.
>
> Please have a try. https://lkml.org/lkml/2017/11/20/118
Hi Wanpeng,
There is shiny new feature being rolled for syzbot, see "#syz test" here:
https://github.com/google/syzkaller/blob/master/docs/syzbot.md#communication-with-syzbot
Please have a try ;)
From 1584576194849866860@xxx Mon Nov 20 09:20:19 +0000 2017
X-GM-THRID: 1582895480167067631
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread
Hi Dmitry,
2017-11-20 12:09 GMT+08:00 Wanpeng Li <[email protected]>:
> 2017-11-18 4:22 GMT+08:00 syzbot
> <bot+d9fbc5c299aa8a95ac07572b4f6e191c0f4efff6@syzkaller.appspotmail.com>:
>> Hello,
>>
>> syzbot has tested the proposed patch but the reproducer still triggered
>> crash:
>> WARNING in kvm_arch_vcpu_ioctl_run
>>
>> VMExit: intr_info=00000000 errcode=00000000 ilen=00000000
>> reason=80000021 qualification=0000000000000000
>> IDTVectoring: info=00000000 errcode=00000000
>> TSC Offset = 0xffffffeeb46bc6ac
>> EPT pointer = 0x00000001ce37601e
>> WARNING: CPU: 0 PID: 3023 at arch/x86/kvm/x86.c:7293
>> kvm_arch_vcpu_ioctl_run+0x213/0x5d20
>> Kernel panic - not syncing: panic_on_warn set ...
>>
>> CPU: 0 PID: 3023 Comm: syz-executor4 Not tainted 4.14.0-next-20171117+ #9
>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
>> Google 01/01/2011
>> Call Trace:
>> dump_stack+0x173/0x237
>> panic+0x1e4/0x41c
>> __warn+0x1d9/0x1f0
>> report_bug+0x20a/0x2d0
>> fixup_bug.part.10+0x32/0x80
>> do_error_trap+0x29c/0x370
>> invalid_op+0x18/0x20
>> RIP: 0010:kvm_arch_vcpu_ioctl_run+0x213/0x5d20
>> RSP: 0018:ffff8801ce197680 EFLAGS: 00010293
>> RAX: ffff8801ce588440 RBX: ffff8801d5b8f000 RCX: ffffffff810d4003
>> RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8801ce0e02b8
>> RBP: ffff8801ce197a50 R08: 0000000000000001 R09: 0000000000000001
>> R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
>> R13: ffff8801ce0e0168 R14: ffff8801cec10980 R15: ffff8801ce0e0080
>> kvm_vcpu_ioctl+0x619/0xf80
>> do_vfs_ioctl+0x18b/0x13e0
>> SyS_ioctl+0x7e/0xb0
>> entry_SYSCALL_64_fastpath+0x1f/0x96
>> RIP: 0033:0x452879
>> RSP: 002b:00007f4bc97fdbe8 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
>> RAX: ffffffffffffffda RBX: 0000000000000082 RCX: 0000000000452879
>> RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000004
>> RBP: 00007ffce1993510 R08: 0000000000000000 R09: 0000000000000000
>> R10: 0000000000000000 R11: 0000000000000212 R12: 0000000000000000
>> R13: 00007ffce199348f R14: 00007f4bc97fe9c0 R15: 0000000000000006
>> Dumping ftrace buffer:
>> (ftrace buffer empty)
>> Kernel Offset: disabled
>> Rebooting in 86400 seconds..
>
> I will have a look.
Please have a try. https://lkml.org/lkml/2017/11/20/118
Regards,
Wanpeng Li
From 1584556684094641180@xxx Mon Nov 20 04:10:12 +0000 2017
X-GM-THRID: 1582895480167067631
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread
2017-11-18 4:22 GMT+08:00 syzbot
<bot+d9fbc5c299aa8a95ac07572b4f6e191c0f4efff6@syzkaller.appspotmail.com>:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered
> crash:
> WARNING in kvm_arch_vcpu_ioctl_run
>
> VMExit: intr_info=00000000 errcode=00000000 ilen=00000000
> reason=80000021 qualification=0000000000000000
> IDTVectoring: info=00000000 errcode=00000000
> TSC Offset = 0xffffffeeb46bc6ac
> EPT pointer = 0x00000001ce37601e
> WARNING: CPU: 0 PID: 3023 at arch/x86/kvm/x86.c:7293
> kvm_arch_vcpu_ioctl_run+0x213/0x5d20
> Kernel panic - not syncing: panic_on_warn set ...
>
> CPU: 0 PID: 3023 Comm: syz-executor4 Not tainted 4.14.0-next-20171117+ #9
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> Call Trace:
> dump_stack+0x173/0x237
> panic+0x1e4/0x41c
> __warn+0x1d9/0x1f0
> report_bug+0x20a/0x2d0
> fixup_bug.part.10+0x32/0x80
> do_error_trap+0x29c/0x370
> invalid_op+0x18/0x20
> RIP: 0010:kvm_arch_vcpu_ioctl_run+0x213/0x5d20
> RSP: 0018:ffff8801ce197680 EFLAGS: 00010293
> RAX: ffff8801ce588440 RBX: ffff8801d5b8f000 RCX: ffffffff810d4003
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8801ce0e02b8
> RBP: ffff8801ce197a50 R08: 0000000000000001 R09: 0000000000000001
> R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
> R13: ffff8801ce0e0168 R14: ffff8801cec10980 R15: ffff8801ce0e0080
> kvm_vcpu_ioctl+0x619/0xf80
> do_vfs_ioctl+0x18b/0x13e0
> SyS_ioctl+0x7e/0xb0
> entry_SYSCALL_64_fastpath+0x1f/0x96
> RIP: 0033:0x452879
> RSP: 002b:00007f4bc97fdbe8 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
> RAX: ffffffffffffffda RBX: 0000000000000082 RCX: 0000000000452879
> RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000004
> RBP: 00007ffce1993510 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000212 R12: 0000000000000000
> R13: 00007ffce199348f R14: 00007f4bc97fe9c0 R15: 0000000000000006
> Dumping ftrace buffer:
> (ftrace buffer empty)
> Kernel Offset: disabled
> Rebooting in 86400 seconds..
I will have a look.
Regards,
Wanpeng Li
From 1584378279897928223@xxx Sat Nov 18 04:54:33 +0000 2017
X-GM-THRID: 1582895480167067631
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread
On Wed, Nov 1, 2017 at 11:05 PM, syzbot
<bot+d9fbc5c299aa8a95ac07572b4f6e191c0f4efff6@syzkaller.appspotmail.com>
wrote:
> Hello,
>
> syzkaller hit the following crash on
> 045c5205823fc3cd4e5cafdedb2cc7d434424909
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
> C reproducer is attached
> syzkaller reproducer is attached. See https://goo.gl/kgGztJ
> for information about syzkaller reproducers
This happens on more recent commits as well, including e.g. upstream
5f479447d983111c039f1d6d958553c1ad1b2ff1(Oct 30):
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6790 at arch/x86/kvm/x86.c:7265
kvm_arch_vcpu_ioctl_run+0x213/0x5c70 arch/x86/kvm/x86.c:7265
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 6790 Comm: syz-executor4 Not tainted 4.14.0-rc7+ #155
Hardware name: Google Google Compute Engine/Google Compute Engine,
BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:16 [inline]
dump_stack+0x194/0x257 lib/dump_stack.c:52
panic+0x1e4/0x417 kernel/panic.c:181
__warn+0x1c4/0x1d9 kernel/panic.c:542
report_bug+0x211/0x2d0 lib/bug.c:183
fixup_bug+0x40/0x90 arch/x86/kernel/traps.c:178
do_trap_no_signal arch/x86/kernel/traps.c:212 [inline]
do_trap+0x260/0x390 arch/x86/kernel/traps.c:261
do_error_trap+0x120/0x390 arch/x86/kernel/traps.c:298
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:311
invalid_op+0x18/0x20 arch/x86/entry/entry_64.S:905
RIP: 0010:kvm_arch_vcpu_ioctl_run+0x213/0x5c70 arch/x86/kvm/x86.c:7265
RSP: 0018:ffff8801c5307670 EFLAGS: 00010212
RAX: 0000000000010000 RBX: ffff8801d2da1000 RCX: ffffc9000244f000
RDX: 000000000000003e RSI: ffffffff810e0713 RDI: ffff8801c6da1160
RBP: ffff8801c5307a40 R08: 1ffff10038db4abb R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000004 R12: 0000000000000000
R13: ffff8801c18d4700 R14: ffff8801c26f1300 R15: ffff8801c6da0f40
kvm_vcpu_ioctl+0x64c/0x1010 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2551
vfs_ioctl fs/ioctl.c:45 [inline]
do_vfs_ioctl+0x1b1/0x1520 fs/ioctl.c:685
SYSC_ioctl fs/ioctl.c:700 [inline]
SyS_ioctl+0x8f/0xc0 fs/ioctl.c:691
entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x452869
RSP: 002b:00007f61c0ff0be8 EFLAGS: 00000212 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000007580d8 RCX: 0000000000452869
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000017
RBP: 0000000000000082 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000212 R12: 00000000006f1580
R13: 00000000ffffffff R14: 00007f61c0ff16d4 R15: 0000000000000001
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..
> EPT pointer = 0x00000001cbc2801e
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 3247 at arch/x86/kvm/x86.c:7265
> kvm_arch_vcpu_ioctl_run+0x213/0x5c70 arch/x86/kvm/x86.c:7265
> Kernel panic - not syncing: panic_on_warn set ...
>
> CPU: 0 PID: 3247 Comm: syzkaller201086 Not tainted 4.14.0-rc2-next-20170927+
> #30
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> Call Trace:
> __dump_stack lib/dump_stack.c:16 [inline]
> dump_stack+0x194/0x257 lib/dump_stack.c:52
> panic+0x1e4/0x417 kernel/panic.c:181
> __warn+0x1c4/0x1d9 kernel/panic.c:542
> report_bug+0x211/0x2d0 lib/bug.c:183
> fixup_bug+0x40/0x90 arch/x86/kernel/traps.c:178
> do_trap_no_signal arch/x86/kernel/traps.c:212 [inline]
> do_trap+0x260/0x390 arch/x86/kernel/traps.c:261
> do_error_trap+0x120/0x390 arch/x86/kernel/traps.c:298
> do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:311
> invalid_op+0x18/0x20 arch/x86/entry/entry_64.S:905
> RIP: 0010:kvm_arch_vcpu_ioctl_run+0x213/0x5c70 arch/x86/kvm/x86.c:7265
> RSP: 0018:ffff8801cb807670 EFLAGS: 00010297
> RAX: ffff8801cbf28280 RBX: ffff8801cbef1000 RCX: ffff8801cd678adc
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8801cd6788f8
> RBP: ffff8801cb807a40 R08: 0000000000000000 R09: 0000000000000001
> R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
> R13: 1ffff10039700f72 R14: ffff8801d6928c00 R15: ffff8801cd6786c0
> kvm_vcpu_ioctl+0x64c/0x1010 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2551
> vfs_ioctl fs/ioctl.c:45 [inline]
> do_vfs_ioctl+0x1b1/0x1530 fs/ioctl.c:685
> SYSC_ioctl fs/ioctl.c:700 [inline]
> SyS_ioctl+0x8f/0xc0 fs/ioctl.c:691
> entry_SYSCALL_64_fastpath+0x1f/0xbe
> RIP: 0033:0x446039
> RSP: 002b:00007f520767adc8 EFLAGS: 00000202 ORIG_RAX: 0000000000000010
> RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000446039
> RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000000f
> RBP: 0000000000000086 R08: 00007f520767b700 R09: 00007f520767b700
> R10: 00007f520767b700 R11: 0000000000000202 R12: 0000000000000000
> R13: 00007ffdb6946c2f R14: 00007f520767b9c0 R15: 0000000000000000
> Dumping ftrace buffer:
> (ftrace buffer empty)
> Kernel Offset: disabled
> Rebooting in 86400 seconds..
>
>
> ---
> This bug is generated by a dumb bot. It may contain errors.
> See https://goo.gl/tpsmEJ for details.
> Direct all questions to [email protected].
> Please credit me with: Reported-by: syzbot <[email protected]>
>
> syzbot will keep track of this bug report.
> Once a fix for this bug is committed, please reply to this email with:
> #syz fix: exact-commit-title
> 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.
>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-bugs/001a114aa95cf6decb055cf1623b%40google.com.
> For more options, visit https://groups.google.com/d/optout.
From 1582895480167067631@xxx Wed Nov 01 20:06:04 +0000 2017
X-GM-THRID: 1582895480167067631
X-Gmail-Labels: Inbox,Category Forums