Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

2017-08-10 1:07 GMT+08:00 Dmitry Vyukov : > 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 >

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

2017-08-10 1:07 GMT+08:00 Dmitry Vyukov : > 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

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

2017-08-10 1:07 GMT+08:00 Dmitry Vyukov : > 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 >

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

2017-08-10 1:07 GMT+08:00 Dmitry Vyukov : > 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

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

On Wed, Aug 9, 2017 at 10:24 PM, David Hildenbrand wrote: > 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

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

On Wed, Aug 9, 2017 at 10:24 PM, David Hildenbrand wrote: > 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

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

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

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

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

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

On Wed, Aug 9, 2017 at 7:09 PM, Dmitry Vyukov wrote: > -non-existent email address > > On Wed, Aug 9, 2017 at 7:07 PM, Dmitry Vyukov wrote: >> Hello, >> >> syzkaller fuzzer has hit the following WARNING in kvm_arch_vcpu_ioctl_run. >> This is easily

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

On Wed, Aug 9, 2017 at 7:09 PM, Dmitry Vyukov wrote: > -non-existent email address > > On Wed, Aug 9, 2017 at 7:07 PM, 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

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

-non-existent email address On Wed, Aug 9, 2017 at 7:07 PM, 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

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

-non-existent email address On Wed, Aug 9, 2017 at 7:07 PM, 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 >

Re: kvm: warning in kvm_load_guest_fpu

2017-05-10 9:48 GMT+08:00 Wanpeng Li : > 2017-05-09 22:04 GMT+08:00 Andrey Konovalov : >> Hi, >> >> I've got the following error report while fuzzing the kernel with syzkaller. >> >> On commit 2868b2513aa732a99ea4a0a6bf10dc93c1f3dac2 (4.11+). >> >> A

Re: kvm: warning in kvm_load_guest_fpu

2017-05-10 9:48 GMT+08:00 Wanpeng Li : > 2017-05-09 22:04 GMT+08:00 Andrey Konovalov : >> Hi, >> >> I've got the following error report while fuzzing the kernel with syzkaller. >> >> On commit 2868b2513aa732a99ea4a0a6bf10dc93c1f3dac2 (4.11+). >> >> A reproducer and .config are attached. > > If

Re: kvm: warning in kvm_load_guest_fpu

2017-05-09 22:04 GMT+08:00 Andrey Konovalov : > Hi, > > I've got the following error report while fuzzing the kernel with syzkaller. > > On commit 2868b2513aa732a99ea4a0a6bf10dc93c1f3dac2 (4.11+). > > A reproducer and .config are attached. If there are beauty codes for

Re: kvm: warning in kvm_load_guest_fpu

2017-05-09 22:04 GMT+08:00 Andrey Konovalov : > Hi, > > I've got the following error report while fuzzing the kernel with syzkaller. > > On commit 2868b2513aa732a99ea4a0a6bf10dc93c1f3dac2 (4.11+). > > A reproducer and .config are attached. If there are beauty codes for testing? > > [

Re: kvm: WARNING in mmu_spte_clear_track_bits

On Tue, Mar 14, 2017 at 4:17 PM, Radim Krčmář wrote: > 2017-03-12 12:20+0100, Dmitry Vyukov: >> On Tue, Jan 17, 2017 at 5:00 PM, Dmitry Vyukov wrote: >>> On Tue, Jan 17, 2017 at 4:20 PM, Paolo Bonzini wrote: On

Re: kvm: WARNING in mmu_spte_clear_track_bits

On Tue, Mar 14, 2017 at 4:17 PM, Radim Krčmář wrote: > 2017-03-12 12:20+0100, Dmitry Vyukov: >> On Tue, Jan 17, 2017 at 5:00 PM, Dmitry Vyukov wrote: >>> On Tue, Jan 17, 2017 at 4:20 PM, Paolo Bonzini wrote: On 13/01/2017 12:15, Dmitry Vyukov wrote: > > I've commented out

Re: kvm: WARNING In kvm_apic_accept_events

On 22.03.2017 16:34, Dmitry Vyukov wrote: > On Wed, Feb 15, 2017 at 11:10 AM, Paolo Bonzini wrote: >> >> >> On 15/02/2017 10:26, David Hildenbrand wrote: Any progress with this? Should we commit this as is? >>> Paolo, should I resend as a proper notcopieddiff

Re: kvm: WARNING In kvm_apic_accept_events

On 22.03.2017 16:34, Dmitry Vyukov wrote: > On Wed, Feb 15, 2017 at 11:10 AM, Paolo Bonzini wrote: >> >> >> On 15/02/2017 10:26, David Hildenbrand wrote: Any progress with this? Should we commit this as is? >>> Paolo, should I resend as a proper notcopieddiff mail? >> >> Yes,

Re: kvm: WARNING In kvm_apic_accept_events

On Wed, Feb 15, 2017 at 11:10 AM, Paolo Bonzini wrote: > > > On 15/02/2017 10:26, David Hildenbrand wrote: >>> >>> Any progress with this? Should we commit this as is? >>> >> Paolo, should I resend as a proper notcopieddiff mail? > > Yes, please do (CCing

Re: kvm: WARNING In kvm_apic_accept_events

On Wed, Feb 15, 2017 at 11:10 AM, Paolo Bonzini wrote: > > > On 15/02/2017 10:26, David Hildenbrand wrote: >>> >>> Any progress with this? Should we commit this as is? >>> >> Paolo, should I resend as a proper notcopieddiff mail? > > Yes, please do (CCing sta...@vger.kernel.org too). > > Paolo

Re: kvm: WARNING in mmu_spte_clear_track_bits

2017-03-12 12:20+0100, Dmitry Vyukov: > On Tue, Jan 17, 2017 at 5:00 PM, Dmitry Vyukov wrote: >> On Tue, Jan 17, 2017 at 4:20 PM, Paolo Bonzini wrote: >>> >>> >>> On 13/01/2017 12:15, Dmitry Vyukov wrote: I've commented out the WARNING for now,

Re: kvm: WARNING in mmu_spte_clear_track_bits

2017-03-12 12:20+0100, Dmitry Vyukov: > On Tue, Jan 17, 2017 at 5:00 PM, Dmitry Vyukov wrote: >> On Tue, Jan 17, 2017 at 4:20 PM, Paolo Bonzini wrote: >>> >>> >>> On 13/01/2017 12:15, Dmitry Vyukov wrote: I've commented out the WARNING for now, but I am seeing lots of

Re: kvm: WARNING in mmu_spte_clear_track_bits

On Tue, Jan 17, 2017 at 5:00 PM, Dmitry Vyukov wrote: > On Tue, Jan 17, 2017 at 4:20 PM, Paolo Bonzini wrote: >> >> >> On 13/01/2017 12:15, Dmitry Vyukov wrote: >>> >>> I've commented out the WARNING for now, but I am seeing lots of >>> use-after-free's

Re: kvm: WARNING in mmu_spte_clear_track_bits

On Tue, Jan 17, 2017 at 5:00 PM, Dmitry Vyukov wrote: > On Tue, Jan 17, 2017 at 4:20 PM, Paolo Bonzini wrote: >> >> >> On 13/01/2017 12:15, Dmitry Vyukov wrote: >>> >>> I've commented out the WARNING for now, but I am seeing lots of >>> use-after-free's and rcu stalls involving

Re: kvm: WARNING in nested_vmx_vmexit

2017-03-02 20:28+0800, Wanpeng Li: > 2017-03-02 2:31 GMT+08:00 Radim Krčmář : >> 2017-03-01 10:44+0100, Dmitry Vyukov: >>> On Wed, Mar 1, 2017 at 7:13 AM, Wanpeng Li wrote: 2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : > Hello,

Re: kvm: WARNING in nested_vmx_vmexit

2017-03-02 20:28+0800, Wanpeng Li: > 2017-03-02 2:31 GMT+08:00 Radim Krčmář : >> 2017-03-01 10:44+0100, Dmitry Vyukov: >>> On Wed, Mar 1, 2017 at 7:13 AM, Wanpeng Li wrote: 2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : > Hello, > > The following program triggers WARNING in

Re: kvm: WARNING in nested_vmx_vmexit

2017-03-02 2:31 GMT+08:00 Radim Krčmář : > 2017-03-01 10:44+0100, Dmitry Vyukov: >> On Wed, Mar 1, 2017 at 7:13 AM, Wanpeng Li wrote: >>> 2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : Hello, The following program triggers

Re: kvm: WARNING in nested_vmx_vmexit

2017-03-02 2:31 GMT+08:00 Radim Krčmář : > 2017-03-01 10:44+0100, Dmitry Vyukov: >> On Wed, Mar 1, 2017 at 7:13 AM, Wanpeng Li wrote: >>> 2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : Hello, The following program triggers WARNING in nested_vmx_vmexit:

Re: kvm: WARNING in nested_vmx_merge_msr_bitmap

2017-02-28 13:07-0800, Jim Mattson: > I believe this happens when the VMCS12 MSR bitmap address is valid, > but no device is configured to respond to the bus request. I agree > that the warning should be removed. However, in this case, the VMCS12 > MSR bitmap should read as all 1s. The same is

Re: kvm: WARNING in nested_vmx_merge_msr_bitmap

2017-02-28 13:07-0800, Jim Mattson: > I believe this happens when the VMCS12 MSR bitmap address is valid, > but no device is configured to respond to the bus request. I agree > that the warning should be removed. However, in this case, the VMCS12 > MSR bitmap should read as all 1s. The same is

Re: kvm: WARNING in nested_vmx_vmexit

2017-03-01 10:44+0100, Dmitry Vyukov: > On Wed, Mar 1, 2017 at 7:13 AM, Wanpeng Li wrote: >> 2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : >>> Hello, >>> >>> The following program triggers WARNING in nested_vmx_vmexit: >>>

Re: kvm: WARNING in nested_vmx_vmexit

2017-03-01 10:44+0100, Dmitry Vyukov: > On Wed, Mar 1, 2017 at 7:13 AM, Wanpeng Li wrote: >> 2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : >>> Hello, >>> >>> The following program triggers WARNING in nested_vmx_vmexit: >>>

Re: kvm: WARNING in nested_vmx_vmexit

2017-02-28 13:48+0100, Dmitry Vyukov: > On Tue, Feb 28, 2017 at 1:15 PM, Dmitry Vyukov wrote: >> Hello, >> >> The following program triggers WARNING in nested_vmx_vmexit: >>

Re: kvm: WARNING in nested_vmx_vmexit

2017-02-28 13:48+0100, Dmitry Vyukov: > On Tue, Feb 28, 2017 at 1:15 PM, Dmitry Vyukov wrote: >> Hello, >> >> The following program triggers WARNING in nested_vmx_vmexit: >>

Re: kvm: WARNING in nested_vmx_vmexit

On Wed, Mar 1, 2017 at 7:13 AM, Wanpeng Li wrote: > 2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : >> Hello, >> >> The following program triggers WARNING in nested_vmx_vmexit: >>

Re: kvm: WARNING in nested_vmx_vmexit

On Wed, Mar 1, 2017 at 7:13 AM, Wanpeng Li wrote: > 2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : >> Hello, >> >> The following program triggers WARNING in nested_vmx_vmexit: >>

Re: kvm: WARNING in nested_vmx_vmexit

2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : > Hello, > > The following program triggers WARNING in nested_vmx_vmexit: > https://gist.githubusercontent.com/dvyukov/16b946d7dc703bb07b9b933f12fb8a6e/raw/dac60506feb8dd9dd22828c486e46ee8a5e30f13/gistfile1.txt > > > [ cut

Re: kvm: WARNING in nested_vmx_vmexit

2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : > Hello, > > The following program triggers WARNING in nested_vmx_vmexit: > https://gist.githubusercontent.com/dvyukov/16b946d7dc703bb07b9b933f12fb8a6e/raw/dac60506feb8dd9dd22828c486e46ee8a5e30f13/gistfile1.txt > > > [ cut here ] >

Re: kvm: WARNING in nested_vmx_merge_msr_bitmap

I believe this happens when the VMCS12 MSR bitmap address is valid, but no device is configured to respond to the bus request. I agree that the warning should be removed. However, in this case, the VMCS12 MSR bitmap should read as all 1s. The same is true everywhere that nested_get_page returns

Re: kvm: WARNING in nested_vmx_merge_msr_bitmap

I believe this happens when the VMCS12 MSR bitmap address is valid, but no device is configured to respond to the bus request. I agree that the warning should be removed. However, in this case, the VMCS12 MSR bitmap should read as all 1s. The same is true everywhere that nested_get_page returns

Re: kvm: WARNING in nested_vmx_vmexit

On Tue, Feb 28, 2017 at 1:15 PM, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in nested_vmx_vmexit: > https://gist.githubusercontent.com/dvyukov/16b946d7dc703bb07b9b933f12fb8a6e/raw/dac60506feb8dd9dd22828c486e46ee8a5e30f13/gistfile1.txt > > >

Re: kvm: WARNING in nested_vmx_vmexit

On Tue, Feb 28, 2017 at 1:15 PM, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in nested_vmx_vmexit: > https://gist.githubusercontent.com/dvyukov/16b946d7dc703bb07b9b933f12fb8a6e/raw/dac60506feb8dd9dd22828c486e46ee8a5e30f13/gistfile1.txt > > > [ cut here

Re: kvm: WARNING In kvm_apic_accept_events

On 15/02/2017 10:26, David Hildenbrand wrote: >> >> Any progress with this? Should we commit this as is? >> > Paolo, should I resend as a proper notcopieddiff mail? Yes, please do (CCing sta...@vger.kernel.org too). Paolo

Re: kvm: WARNING In kvm_apic_accept_events

On 15/02/2017 10:26, David Hildenbrand wrote: >> >> Any progress with this? Should we commit this as is? >> > Paolo, should I resend as a proper notcopieddiff mail? Yes, please do (CCing sta...@vger.kernel.org too). Paolo

Re: kvm: WARNING In kvm_apic_accept_events

>>> From: David Hildenbrand >>> Date: Mon, 23 Jan 2017 16:42:23 +0100 >>> Subject: [PATCH] KVM: x86: fix illegal MP_STATE when in/entering SMM >>> >>> If we already entered/are about to enter SMM, don't allow >>> switching to INIT/SIPI_RECEIVED, otherwise the next call to >>>

Re: kvm: WARNING In kvm_apic_accept_events

>>> From: David Hildenbrand >>> Date: Mon, 23 Jan 2017 16:42:23 +0100 >>> Subject: [PATCH] KVM: x86: fix illegal MP_STATE when in/entering SMM >>> >>> If we already entered/are about to enter SMM, don't allow >>> switching to INIT/SIPI_RECEIVED, otherwise the next call to >>>

Re: kvm: WARNING In kvm_apic_accept_events

On Mon, Jan 23, 2017 at 5:29 PM, Paolo Bonzini wrote: > > On 23/01/2017 17:03, David Hildenbrand wrote: >> Am 22.01.2017 um 09:52 schrieb Dmitry Vyukov: >>> On Sat, Nov 12, 2016 at 2:56 AM, Dmitry Vyukov wrote: Hello, The following program

Re: kvm: WARNING In kvm_apic_accept_events

On Mon, Jan 23, 2017 at 5:29 PM, Paolo Bonzini wrote: > > On 23/01/2017 17:03, David Hildenbrand wrote: >> Am 22.01.2017 um 09:52 schrieb Dmitry Vyukov: >>> On Sat, Nov 12, 2016 at 2:56 AM, Dmitry Vyukov wrote: Hello, The following program triggers WARNING in

Re: kvm: WARNING In kvm_apic_accept_events

On 23/01/2017 17:03, David Hildenbrand wrote: > Am 22.01.2017 um 09:52 schrieb Dmitry Vyukov: >> On Sat, Nov 12, 2016 at 2:56 AM, Dmitry Vyukov wrote: >>> Hello, >>> >>> The following program triggers WARNING in kvm_apic_accept_events: >>>

Re: kvm: WARNING In kvm_apic_accept_events

On 23/01/2017 17:03, David Hildenbrand wrote: > Am 22.01.2017 um 09:52 schrieb Dmitry Vyukov: >> On Sat, Nov 12, 2016 at 2:56 AM, Dmitry Vyukov wrote: >>> Hello, >>> >>> The following program triggers WARNING in kvm_apic_accept_events: >>>

Re: kvm: WARNING In kvm_apic_accept_events

Am 22.01.2017 um 09:52 schrieb Dmitry Vyukov: > On Sat, Nov 12, 2016 at 2:56 AM, Dmitry Vyukov wrote: >> Hello, >> >> The following program triggers WARNING in kvm_apic_accept_events: >>

Re: kvm: WARNING In kvm_apic_accept_events

Am 22.01.2017 um 09:52 schrieb Dmitry Vyukov: > On Sat, Nov 12, 2016 at 2:56 AM, Dmitry Vyukov wrote: >> Hello, >> >> The following program triggers WARNING in kvm_apic_accept_events: >>

Re: kvm: WARNING In kvm_apic_accept_events

On Sat, Nov 12, 2016 at 2:56 AM, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in kvm_apic_accept_events: > https://gist.githubusercontent.com/dvyukov/95b845a2e637485568ea1ef181a72370/raw/d90717dd67128b21715c5e794568a1600f613d97/gistfile1.txt > > On

Re: kvm: WARNING In kvm_apic_accept_events

On Sat, Nov 12, 2016 at 2:56 AM, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in kvm_apic_accept_events: > https://gist.githubusercontent.com/dvyukov/95b845a2e637485568ea1ef181a72370/raw/d90717dd67128b21715c5e794568a1600f613d97/gistfile1.txt > > On commit

Re: kvm: WARNING in kvm_load_guest_fpu

On Sat, Nov 12, 2016 at 4:57 AM, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in kvm_load_guest_fpu: > https://gist.githubusercontent.com/dvyukov/5bc076073b48772e22b5f33acbe2b743/raw/1000df869f0d58a5c6e637268453c711280b255d/gistfile1.txt > > On

Re: kvm: WARNING in kvm_load_guest_fpu

On Sat, Nov 12, 2016 at 4:57 AM, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in kvm_load_guest_fpu: > https://gist.githubusercontent.com/dvyukov/5bc076073b48772e22b5f33acbe2b743/raw/1000df869f0d58a5c6e637268453c711280b255d/gistfile1.txt > > On commit

Re: kvm: WARNING in mmu_spte_clear_track_bits

On Tue, Jan 17, 2017 at 4:20 PM, Paolo Bonzini wrote: > > > On 13/01/2017 12:15, Dmitry Vyukov wrote: >> >> I've commented out the WARNING for now, but I am seeing lots of >> use-after-free's and rcu stalls involving mmu_spte_clear_track_bits: >> >> >> BUG: KASAN:

Re: kvm: WARNING in mmu_spte_clear_track_bits

On Tue, Jan 17, 2017 at 4:20 PM, Paolo Bonzini wrote: > > > On 13/01/2017 12:15, Dmitry Vyukov wrote: >> >> I've commented out the WARNING for now, but I am seeing lots of >> use-after-free's and rcu stalls involving mmu_spte_clear_track_bits: >> >> >> BUG: KASAN: use-after-free in

Re: kvm: WARNING in mmu_spte_clear_track_bits

On 13/01/2017 12:15, Dmitry Vyukov wrote: > > I've commented out the WARNING for now, but I am seeing lots of > use-after-free's and rcu stalls involving mmu_spte_clear_track_bits: > > > BUG: KASAN: use-after-free in mmu_spte_clear_track_bits+0x186/0x190 > arch/x86/kvm/mmu.c:597 at addr

Re: kvm: WARNING in mmu_spte_clear_track_bits

On 13/01/2017 12:15, Dmitry Vyukov wrote: > > I've commented out the WARNING for now, but I am seeing lots of > use-after-free's and rcu stalls involving mmu_spte_clear_track_bits: > > > BUG: KASAN: use-after-free in mmu_spte_clear_track_bits+0x186/0x190 > arch/x86/kvm/mmu.c:597 at addr

Re: kvm: WARNING in x86_emulate_insn

On Tue, Jan 17, 2017 at 12:34 PM, Dmitry Vyukov wrote: > On Fri, Jan 13, 2017 at 6:47 PM, Radim Krčmář wrote: >> 2017-01-12 14:55+0100, Dmitry Vyukov: >>> Hello, >>> >>> I've got the following WARNING in x86_emulate_insn while running >>> syzkaller fuzzer:

Re: kvm: WARNING in x86_emulate_insn

On Tue, Jan 17, 2017 at 12:34 PM, Dmitry Vyukov wrote: > On Fri, Jan 13, 2017 at 6:47 PM, Radim Krčmář wrote: >> 2017-01-12 14:55+0100, Dmitry Vyukov: >>> Hello, >>> >>> I've got the following WARNING in x86_emulate_insn while running >>> syzkaller fuzzer: >>> >>> WARNING: CPU: 2 PID: 18646 at

Re: kvm: WARNING in x86_emulate_insn

On Fri, Jan 13, 2017 at 6:47 PM, Radim Krčmář wrote: > 2017-01-12 14:55+0100, Dmitry Vyukov: >> Hello, >> >> I've got the following WARNING in x86_emulate_insn while running >> syzkaller fuzzer: >> >> WARNING: CPU: 2 PID: 18646 at arch/x86/kvm/emulate.c:5558 >>

Re: kvm: WARNING in x86_emulate_insn

On Fri, Jan 13, 2017 at 6:47 PM, Radim Krčmář wrote: > 2017-01-12 14:55+0100, Dmitry Vyukov: >> Hello, >> >> I've got the following WARNING in x86_emulate_insn while running >> syzkaller fuzzer: >> >> WARNING: CPU: 2 PID: 18646 at arch/x86/kvm/emulate.c:5558 >> x86_emulate_insn+0x16a5/0x4090

Re: kvm: WARNING in x86_emulate_insn

2017-01-12 14:55+0100, Dmitry Vyukov: > Hello, > > I've got the following WARNING in x86_emulate_insn while running > syzkaller fuzzer: > > WARNING: CPU: 2 PID: 18646 at arch/x86/kvm/emulate.c:5558 > x86_emulate_insn+0x16a5/0x4090 arch/x86/kvm/emulate.c:5572 > Modules linked in: > CPU: 2 PID:

Re: kvm: WARNING in x86_emulate_insn

2017-01-12 14:55+0100, Dmitry Vyukov: > Hello, > > I've got the following WARNING in x86_emulate_insn while running > syzkaller fuzzer: > > WARNING: CPU: 2 PID: 18646 at arch/x86/kvm/emulate.c:5558 > x86_emulate_insn+0x16a5/0x4090 arch/x86/kvm/emulate.c:5572 > Modules linked in: > CPU: 2 PID:

Re: kvm: WARNING in mmu_spte_clear_track_bits

On Tue, Dec 13, 2016 at 8:50 PM, Dmitry Vyukov wrote: > Hello, > > The following program: > https://gist.githubusercontent.com/dvyukov/23d8bd622fd526d7701ac2057bbbc9c2/raw/aacd20451e6f460232f5e1da262b653fb3155613/gistfile1.txt > > leads to WARNING in mmu_spte_clear_track_bits

Re: kvm: WARNING in mmu_spte_clear_track_bits

On Tue, Dec 13, 2016 at 8:50 PM, Dmitry Vyukov wrote: > Hello, > > The following program: > https://gist.githubusercontent.com/dvyukov/23d8bd622fd526d7701ac2057bbbc9c2/raw/aacd20451e6f460232f5e1da262b653fb3155613/gistfile1.txt > > leads to WARNING in mmu_spte_clear_track_bits and later to splash

Re: kvm: WARNING in em_jmp_far

On 15/11/2016 06:39, Nadav Amit wrote: > >> On Nov 14, 2016, at 9:30 PM, Dmitry Vyukov wrote: >> >> On Tue, Nov 15, 2016 at 6:24 AM, Nadav Amit wrote: >>> On Nov 14, 2016, at 9:06 PM, Dmitry Vyukov wrote: Hello,

Re: kvm: WARNING in em_jmp_far

On 15/11/2016 06:39, Nadav Amit wrote: > >> On Nov 14, 2016, at 9:30 PM, Dmitry Vyukov wrote: >> >> On Tue, Nov 15, 2016 at 6:24 AM, Nadav Amit wrote: >>> On Nov 14, 2016, at 9:06 PM, Dmitry Vyukov wrote: Hello, The following program triggers WARNING in em_jmp_far:

Re: kvm: WARNING in em_jmp_far

> On Nov 14, 2016, at 9:30 PM, Dmitry Vyukov wrote: > > On Tue, Nov 15, 2016 at 6:24 AM, Nadav Amit wrote: >> >>> On Nov 14, 2016, at 9:06 PM, Dmitry Vyukov wrote: >>> >>> Hello, >>> >>> The following program triggers WARNING in

Re: kvm: WARNING in em_jmp_far

> On Nov 14, 2016, at 9:30 PM, Dmitry Vyukov wrote: > > On Tue, Nov 15, 2016 at 6:24 AM, Nadav Amit wrote: >> >>> On Nov 14, 2016, at 9:06 PM, Dmitry Vyukov wrote: >>> >>> Hello, >>> >>> The following program triggers WARNING in em_jmp_far: >>>

Re: kvm: WARNING in em_jmp_far

> On Nov 14, 2016, at 9:06 PM, Dmitry Vyukov wrote: > > Hello, > > The following program triggers WARNING in em_jmp_far: > https://gist.githubusercontent.com/dvyukov/16bfd3d68fa7d5461101ef74e07796e4/raw/e6d663980681f2c5838ff6cd361cede7d3204838/gistfile1.txt > > >

Re: kvm: WARNING in em_jmp_far

> On Nov 14, 2016, at 9:06 PM, Dmitry Vyukov wrote: > > Hello, > > The following program triggers WARNING in em_jmp_far: > https://gist.githubusercontent.com/dvyukov/16bfd3d68fa7d5461101ef74e07796e4/raw/e6d663980681f2c5838ff6cd361cede7d3204838/gistfile1.txt > > > WARNING: CPU: 1 PID: 15748

Re: kvm: WARNING in em_jmp_far

On Tue, Nov 15, 2016 at 6:24 AM, Nadav Amit wrote: > >> On Nov 14, 2016, at 9:06 PM, Dmitry Vyukov wrote: >> >> Hello, >> >> The following program triggers WARNING in em_jmp_far: >>

Re: kvm: WARNING in em_jmp_far

On Tue, Nov 15, 2016 at 6:24 AM, Nadav Amit wrote: > >> On Nov 14, 2016, at 9:06 PM, Dmitry Vyukov wrote: >> >> Hello, >> >> The following program triggers WARNING in em_jmp_far: >>

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

On 14/11/2016 15:09, Dmitry Vyukov wrote: > > I made dump_vmcs() no-op locally. You should see the warning > regardless, but probably it is difficult to notice. Or maybe tons of > output affect timings so that the warning does not happen. I let it run for several minutes, and only got 50

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

On 14/11/2016 15:09, Dmitry Vyukov wrote: > > I made dump_vmcs() no-op locally. You should see the warning > regardless, but probably it is difficult to notice. Or maybe tons of > output affect timings so that the warning does not happen. I let it run for several minutes, and only got 50

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

On Mon, Nov 14, 2016 at 3:03 PM, Paolo Bonzini wrote: > > > On 14/11/2016 15:00, Dmitry Vyukov wrote: >> Hello, >> >> The following program triggers WARNING in kvm_arch_vcpu_ioctl_run in >> run in parallel loop: >>

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

On Mon, Nov 14, 2016 at 3:03 PM, Paolo Bonzini wrote: > > > On 14/11/2016 15:00, Dmitry Vyukov wrote: >> Hello, >> >> The following program triggers WARNING in kvm_arch_vcpu_ioctl_run in >> run in parallel loop: >>

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

On 14/11/2016 15:00, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in kvm_arch_vcpu_ioctl_run in > run in parallel loop: > https://gist.githubusercontent.com/dvyukov/08091eee6f38548ff9e6905c5e0eaaee/raw/8cae95f2e88eeb98c4ddc06d227670c1e248222f/gistfile1.txt > > On

Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run

On 14/11/2016 15:00, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in kvm_arch_vcpu_ioctl_run in > run in parallel loop: > https://gist.githubusercontent.com/dvyukov/08091eee6f38548ff9e6905c5e0eaaee/raw/8cae95f2e88eeb98c4ddc06d227670c1e248222f/gistfile1.txt > > On

Re: kvm: WARNING in em_ret_far

Reproduced. Paolo On 12/11/2016 22:31, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in em_ret_far: > https://gist.githubusercontent.com/dvyukov/12bc06a5f638d91953f94bcbe49bcc89/raw/6d863470808a695c085620664b7134864b2eb2a9/gistfile1.txt > > On commit

Re: kvm: WARNING in em_ret_far

Reproduced. Paolo On 12/11/2016 22:31, Dmitry Vyukov wrote: > Hello, > > The following program triggers WARNING in em_ret_far: > https://gist.githubusercontent.com/dvyukov/12bc06a5f638d91953f94bcbe49bcc89/raw/6d863470808a695c085620664b7134864b2eb2a9/gistfile1.txt > > On commit

Re: KVM: WARNING: at .. kvm_release_pfn_clean

On 10/05/2012 04:33 PM, Jiri Slaby wrote: > Hi, > > I'm getting this warning while running qemu-kvm 1.2.rc1 on the top of > 3.6.0-next-20121001: > WARNING: at virt/kvm/kvm_main.c:1325 kvm_release_pfn_clean+0x70/0x80() > Hardware name: To Be Filled By O.E.M. > Modules linked in: nls_cp437 vfat fat

Re: KVM: WARNING: at .. kvm_release_pfn_clean

On 10/05/2012 04:33 PM, Jiri Slaby wrote: Hi, I'm getting this warning while running qemu-kvm 1.2.rc1 on the top of 3.6.0-next-20121001: WARNING: at virt/kvm/kvm_main.c:1325 kvm_release_pfn_clean+0x70/0x80() Hardware name: To Be Filled By O.E.M. Modules linked in: nls_cp437 vfat fat

RE: kvm warning

On Mon, 13 Aug 2007, Luck, Tony wrote: > > Solution (1) above sounds preferable, unless there are mysterious reasons > > why ia64 wants to avoid Kconfig.preempt (adding Tony Luck to Cc:). > > Send me a patch and unless it causes more problems than it solves, I'll > put it in. [PATCH] ia64:

RE: kvm warning

> Solution (1) above sounds preferable, unless there are mysterious reasons > why ia64 wants to avoid Kconfig.preempt (adding Tony Luck to Cc:). Send me a patch and unless it causes more problems than it solves, I'll put it in. -Tony - To unsubscribe from this list: send the line "unsubscribe

Re: kvm warning

On 8/9/07, Avi Kivity <[EMAIL PROTECTED]> wrote: > Andrew Morton wrote: > > On Thu, 09 Aug 2007 01:48:07 +0300 > > Avi Kivity <[EMAIL PROTECTED]> wrote: > > > >> Ingo Molnar wrote: > >> > >>> * Andrew Morton <[EMAIL PROTECTED]> wrote: > >>> > ia64 allmodconfig says > >

Re: kvm warning

On 8/9/07, Avi Kivity [EMAIL PROTECTED] wrote: Andrew Morton wrote: On Thu, 09 Aug 2007 01:48:07 +0300 Avi Kivity [EMAIL PROTECTED] wrote: Ingo Molnar wrote: * Andrew Morton [EMAIL PROTECTED] wrote: ia64 allmodconfig says drivers/kvm/Kconfig:14:warning: 'select' used by config

RE: kvm warning

Solution (1) above sounds preferable, unless there are mysterious reasons why ia64 wants to avoid Kconfig.preempt (adding Tony Luck to Cc:). Send me a patch and unless it causes more problems than it solves, I'll put it in. -Tony - To unsubscribe from this list: send the line unsubscribe

RE: kvm warning

On Mon, 13 Aug 2007, Luck, Tony wrote: Solution (1) above sounds preferable, unless there are mysterious reasons why ia64 wants to avoid Kconfig.preempt (adding Tony Luck to Cc:). Send me a patch and unless it causes more problems than it solves, I'll put it in. [PATCH] ia64: Include

Re: kvm warning

Andrew Morton wrote: On Thu, 09 Aug 2007 01:48:07 +0300 Avi Kivity <[EMAIL PROTECTED]> wrote: Ingo Molnar wrote: * Andrew Morton <[EMAIL PROTECTED]> wrote: ia64 allmodconfig says drivers/kvm/Kconfig:14:warning: 'select' used by config symbol 'KVM' refers to undefined

Re: kvm warning

On Thu, 09 Aug 2007 01:48:07 +0300 Avi Kivity <[EMAIL PROTECTED]> wrote: > Ingo Molnar wrote: > > * Andrew Morton <[EMAIL PROTECTED]> wrote: > > > > > >> ia64 allmodconfig says > >> > >> drivers/kvm/Kconfig:14:warning: 'select' used by config symbol 'KVM' > >> refers to undefined symbol

Re: kvm warning

Ingo Molnar wrote: * Andrew Morton <[EMAIL PROTECTED]> wrote: ia64 allmodconfig says drivers/kvm/Kconfig:14:warning: 'select' used by config symbol 'KVM' refers to undefined symbol 'PREEMPT_NOTIFIERS' hm, why doesnt ia64 pick up kernel/Kconfig.preempt, like all the other arches?

Re: kvm warning

* Andrew Morton <[EMAIL PROTECTED]> wrote: > ia64 allmodconfig says > > drivers/kvm/Kconfig:14:warning: 'select' used by config symbol 'KVM' > refers to undefined symbol 'PREEMPT_NOTIFIERS' hm, why doesnt ia64 pick up kernel/Kconfig.preempt, like all the other arches? Due to that ia64 also

Re: kvm warning

* Andrew Morton [EMAIL PROTECTED] wrote: ia64 allmodconfig says drivers/kvm/Kconfig:14:warning: 'select' used by config symbol 'KVM' refers to undefined symbol 'PREEMPT_NOTIFIERS' hm, why doesnt ia64 pick up kernel/Kconfig.preempt, like all the other arches? Due to that ia64 also misses

Re: kvm warning

Ingo Molnar wrote: * Andrew Morton [EMAIL PROTECTED] wrote: ia64 allmodconfig says drivers/kvm/Kconfig:14:warning: 'select' used by config symbol 'KVM' refers to undefined symbol 'PREEMPT_NOTIFIERS' hm, why doesnt ia64 pick up kernel/Kconfig.preempt, like all the other arches? Due

  1   2   >