Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <CACT4Y+YtgtYXoOF3p+mOZdKYHXDgakaczgK_kFF7H0UCioP6dg@mail.gmail.com>
References: <001a114aa95cf6decb055cf1623b@google.com> <001a113ebb3240667d055e337d48@google.com>
 <CANRm+CwOti9F4Fitr5TvX+ji8s807n_kGXe_p=SPe5tp27=3mw@mail.gmail.com>
 <CANRm+CyZZJDbKNwu25ZCf0LhZizUfcehZqoO=SiqS0r_H51=Zg@mail.gmail.com>
 <CACT4Y+YYHcZqeprx-aXjqncnED4d8UhyOiU3ygeVVQ-JvOtSQg@mail.gmail.com> <CACT4Y+YtgtYXoOF3p+mOZdKYHXDgakaczgK_kFF7H0UCioP6dg@mail.gmail.com>
From:   Wanpeng Li <kernellwp@gmail.com>
Date:   Mon, 20 Nov 2017 20:13:29 +0800
Message-ID: <CANRm+Cx_eP9q79_mfhTtXmutyoyiiS7R6j73Mi17Nnt7R2KGMQ@mail.gmail.com>
Subject: Re: WARNING in kvm_arch_vcpu_ioctl_run (2)
To:     Dmitry Vyukov <dvyukov@google.com>
Cc:     "H. Peter Anvin" <hpa@zytor.com>,
        syzbot 
        <bot+d9fbc5c299aa8a95ac07572b4f6e191c0f4efff6@syzkaller.appspotmail.com>,
        kvm <kvm@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Ingo Molnar <mingo@redhat.com>,
        Paolo Bonzini <pbonzini@redhat.com>,
        Radim Krcmar <rkrcmar@redhat.com>,
        syzkaller-bugs@googlegroups.com,
        Thomas Gleixner <tglx@linutronix.de>,
        "the arch/x86 maintainers" <x86@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

2017-11-20 20:06 GMT+08:00 Dmitry Vyukov <dvyukov@google.com>:
> On Mon, Nov 20, 2017 at 10:23 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
>> On Mon, Nov 20, 2017 at 10:19 AM, Wanpeng Li <kernellwp@gmail.com> wrote:
>>> Hi Dmitry,
>>> 2017-11-20 12:09 GMT+08:00 Wanpeng Li <kernellwp@gmail.com>:
>>>> 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