From: David Hildenbrand <david@redhat.com>
To: "Dmitry Vyukov" <dvyukov@google.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"KVM list" <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, "P J P" <ppandit@redhat.com>,
"James Mattson" <jmattson@google.com>,
"Xiao Guangrong" <guangrong.xiao@linux.intel.com>,
"Haozhong Zhang" <haozhong.zhang@intel.com>,
"Wanpeng Li" <kernellwp@gmail.com>,
"Steve Rutherford" <srutherford@google.com>
Cc: syzkaller <syzkaller@googlegroups.com>
Subject: Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run
Date: Wed, 9 Aug 2017 22:24:32 +0200 [thread overview]
Message-ID: <43b663ae-2b6b-d6ca-b41f-a35247551953@redhat.com> (raw)
In-Reply-To: <CACT4Y+YJSqvBLuM_UnzHNganNUT-FnsgtCg_Hk2+2JBCoiO0qA@mail.gmail.com>
On 09.08.2017 19:07, Dmitry Vyukov wrote:
> Hello,
>
> syzkaller fuzzer has hit the following WARNING in kvm_arch_vcpu_ioctl_run.
> This is easily reproducible and reproducer is attached at the bottom.
> The report is on upstream commit
> 26c5cebfdb6ca799186f1e56be7d6f2480c5012c. This requires setting
> kvm-intel.unrestricted_guest=0 on the machine, with
> unrestricted_guest=1 the WARNING does not happen. Output of the
> program is:
>
> ret1=0 exit_reason=17 suberror=1
> ret2=0 exit_reason=8 suberror=65530
>
>
I wonder if the following is possible:
1) we set vcpu->arch.pio.count != 0
2) we set vcpu->arch.complete_userspace_io = complete_emulated_pio;
(in x86_emulate_instruction)
3) in kvm_arch_vcpu_ioctl_run(), we execute
vcpu->arch.complete_userspace_io and set it to NULL.
4. complete_emulated_pio() calls complete_emulated_io(), which fails
(in some different way) and leaves vcpu->arch.pio.count set.
5. we now have vcpu->arch.pio.count set but
vcpu->arch.complete_userspace_io cleared.
Same should not apply to vcpu->mmio_needed, as we clear it before
calling complete_emulated_io() in complete_emulated_mmio().
AFAIK, we cannot simply clear vcpu->arch.pio.count before calling
complete_emulated_io().
Maybe something like this could help: (untested, wild guess)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 86242ee..60296fef 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -7227,10 +7227,14 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu *vcpu, struct kvm_run *kvm_run)
int (*cui)(struct kvm_vcpu *) = vcpu->arch.complete_userspace_io;
vcpu->arch.complete_userspace_io = NULL;
r = cui(vcpu);
+ if (!vcpu->arch.complete_userspace_io) {
+ /* no new handler -> everything handled */
+ vcpu->arch.pio.count = 0;
+ vcpu->mmio_needed = 0;
+ }
if (r <= 0)
goto out;
- } else
- WARN_ON(vcpu->arch.pio.count || vcpu->mmio_needed);
+ }
if (kvm_run->immediate_exit)
r = -EINTR;
Alternatively, something like this
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 86242ee..58be388 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -7127,9 +7127,15 @@ static inline int complete_emulated_io(struct kvm_vcpu *vcpu)
static int complete_emulated_pio(struct kvm_vcpu *vcpu)
{
+ int ret;
+
BUG_ON(!vcpu->arch.pio.count);
- return complete_emulated_io(vcpu);
+ ret = complete_emulated_io(vcpu);
+ if (ret && !vcpu->arch.complete_userspace_io)
+ vcpu->arch.pio.count = 0;
+
+ return ret;
}
/*
Haven't tried to reproduce on upstream yet (at least on my Fedora 25
I can't trigger it), so only wild guesses.
--
Thanks,
David
next prev parent reply other threads:[~2017-08-09 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 17:07 Dmitry Vyukov
2017-08-09 17:09 ` Dmitry Vyukov
2017-08-09 17:11 ` Dmitry Vyukov
2017-08-09 20:24 ` David Hildenbrand [this message]
2017-08-09 20:35 ` Dmitry Vyukov
2017-08-09 21:53 ` Wanpeng Li
2017-08-10 5:37 ` Wanpeng Li
-- strict thread matches above, loose matches on Subject: below --
2016-11-14 14:00 Dmitry Vyukov
2016-11-14 14:03 ` Paolo Bonzini
2016-11-14 14:09 ` Dmitry Vyukov
2016-11-14 14:45 ` Paolo Bonzini
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=43b663ae-2b6b-d6ca-b41f-a35247551953@redhat.com \
--to=david@redhat.com \
--cc=dvyukov@google.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=haozhong.zhang@intel.com \
--cc=jmattson@google.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=ppandit@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=srutherford@google.com \
--cc=syzkaller@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
all inboxes | Powered by JetHome®