From: Paolo Bonzini <pbonzini@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: kvm@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
qemu-devel@nongnu.org
Subject: Re: freeze host when injecting NMIs in the guest, at least in 4.4-rc4+
Date: Thu, 10 Dec 2015 18:34:22 +0100 [thread overview]
Message-ID: <5669B79E.4000906@redhat.com> (raw)
In-Reply-To: <20151210165340.GA3831@pd.tnic>
On 10/12/2015 17:53, Borislav Petkov wrote:
> Just did, there it splats even when booting the guest, without even
> injecting NMIs:
>
> [ 113.233992] ===============================
> [ 113.238192] [ INFO: suspicious RCU usage. ]
> [ 113.242393] 4.4.0-rc4+ #1 Not tainted
> [ 113.246056] -------------------------------
> [ 113.250257] arch/x86/kvm/trace.h:29 suspicious rcu_dereference_check() usage!
> [ 113.257400]
> other info that might help us debug this:
>
> [ 113.265432]
> RCU used illegally from idle CPU!
> rcu_scheduler_active = 1, debug_locks = 0
> [ 113.276321] RCU used illegally from extended quiescent state!
> [ 113.282083] 1 lock held by qemu-system-x86/2275:
> [ 113.286711] #0: (&vcpu->mutex){+.+.+.}, at: [<ffffffffa01d472c>] vcpu_load+0x1c/0x80 [kvm]
> [ 113.295270]
> stack backtrace:
> [ 113.299644] CPU: 4 PID: 2275 Comm: qemu-system-x86 Not tainted 4.4.0-rc4+ #1
> [ 113.306706] Hardware name: Dell Inc. Precision T3600/0PTTT9, BIOS A13 05/11/2014
> [ 113.314122] 0000000000000001 ffff88042f263d28 ffffffff813c2cfc ffff880432d53000
> [ 113.321575] ffff88042f263d58 ffffffff810c5157 ffff88042f268000 0000000000000000
> [ 113.329027] 0000000000000000 0000000000000001 ffff88042f263e10 ffffffffa01ee7c8
> [ 113.336483] Call Trace:
> [ 113.338939] [<ffffffff813c2cfc>] dump_stack+0x4e/0x82
> [ 113.344098] [<ffffffff810c5157>] lockdep_rcu_suspicious+0xe7/0x120
> [ 113.350385] [<ffffffffa01ee7c8>] kvm_arch_vcpu_ioctl_run+0x16f8/0x19c0 [kvm]
> [ 113.357544] [<ffffffffa01ed1a0>] ? kvm_arch_vcpu_ioctl_run+0xd0/0x19c0 [kvm]
> [ 113.364695] [<ffffffffa01d4b32>] kvm_vcpu_ioctl+0x342/0x700 [kvm]
> [ 113.370896] [<ffffffff810c4a7d>] ? __lock_is_held+0x4d/0x70
> [ 113.376583] [<ffffffff812351ae>] ? __fget+0xfe/0x200
> [ 113.381662] [<ffffffff812291f1>] do_vfs_ioctl+0x301/0x550
> [ 113.387156] [<ffffffff8123531a>] ? __fget_light+0x2a/0x90
> [ 113.392654] [<ffffffff81229481>] SyS_ioctl+0x41/0x70
> [ 113.397739] [<ffffffff8185cb36>] entry_SYSCALL_64_fastpath+0x16/0x7a
> [ 113.755008] kvm: zapping shadow pages for mmio generation wraparound
Wow, this must have been there forever...
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] freeze host when injecting NMIs in the guest, at least in 4.4-rc4+
Date: Thu, 10 Dec 2015 18:34:22 +0100 [thread overview]
Message-ID: <5669B79E.4000906@redhat.com> (raw)
In-Reply-To: <20151210165340.GA3831@pd.tnic>
On 10/12/2015 17:53, Borislav Petkov wrote:
> Just did, there it splats even when booting the guest, without even
> injecting NMIs:
>
> [ 113.233992] ===============================
> [ 113.238192] [ INFO: suspicious RCU usage. ]
> [ 113.242393] 4.4.0-rc4+ #1 Not tainted
> [ 113.246056] -------------------------------
> [ 113.250257] arch/x86/kvm/trace.h:29 suspicious rcu_dereference_check() usage!
> [ 113.257400]
> other info that might help us debug this:
>
> [ 113.265432]
> RCU used illegally from idle CPU!
> rcu_scheduler_active = 1, debug_locks = 0
> [ 113.276321] RCU used illegally from extended quiescent state!
> [ 113.282083] 1 lock held by qemu-system-x86/2275:
> [ 113.286711] #0: (&vcpu->mutex){+.+.+.}, at: [<ffffffffa01d472c>] vcpu_load+0x1c/0x80 [kvm]
> [ 113.295270]
> stack backtrace:
> [ 113.299644] CPU: 4 PID: 2275 Comm: qemu-system-x86 Not tainted 4.4.0-rc4+ #1
> [ 113.306706] Hardware name: Dell Inc. Precision T3600/0PTTT9, BIOS A13 05/11/2014
> [ 113.314122] 0000000000000001 ffff88042f263d28 ffffffff813c2cfc ffff880432d53000
> [ 113.321575] ffff88042f263d58 ffffffff810c5157 ffff88042f268000 0000000000000000
> [ 113.329027] 0000000000000000 0000000000000001 ffff88042f263e10 ffffffffa01ee7c8
> [ 113.336483] Call Trace:
> [ 113.338939] [<ffffffff813c2cfc>] dump_stack+0x4e/0x82
> [ 113.344098] [<ffffffff810c5157>] lockdep_rcu_suspicious+0xe7/0x120
> [ 113.350385] [<ffffffffa01ee7c8>] kvm_arch_vcpu_ioctl_run+0x16f8/0x19c0 [kvm]
> [ 113.357544] [<ffffffffa01ed1a0>] ? kvm_arch_vcpu_ioctl_run+0xd0/0x19c0 [kvm]
> [ 113.364695] [<ffffffffa01d4b32>] kvm_vcpu_ioctl+0x342/0x700 [kvm]
> [ 113.370896] [<ffffffff810c4a7d>] ? __lock_is_held+0x4d/0x70
> [ 113.376583] [<ffffffff812351ae>] ? __fget+0xfe/0x200
> [ 113.381662] [<ffffffff812291f1>] do_vfs_ioctl+0x301/0x550
> [ 113.387156] [<ffffffff8123531a>] ? __fget_light+0x2a/0x90
> [ 113.392654] [<ffffffff81229481>] SyS_ioctl+0x41/0x70
> [ 113.397739] [<ffffffff8185cb36>] entry_SYSCALL_64_fastpath+0x16/0x7a
> [ 113.755008] kvm: zapping shadow pages for mmio generation wraparound
Wow, this must have been there forever...
Paolo
next prev parent reply other threads:[~2015-12-10 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 14:04 ext4/jbd splat in 4.4-rc4+ Borislav Petkov
2015-12-10 16:27 ` Borislav Petkov
2015-12-10 16:44 ` freeze host when injecting NMIs in the guest, at least " Borislav Petkov
2015-12-10 16:44 ` [Qemu-devel] " Borislav Petkov
2015-12-10 16:49 ` Paolo Bonzini
2015-12-10 16:49 ` [Qemu-devel] " Paolo Bonzini
2015-12-10 16:53 ` Borislav Petkov
2015-12-10 16:53 ` [Qemu-devel] " Borislav Petkov
2015-12-10 17:34 ` Paolo Bonzini [this message]
2015-12-10 17:34 ` 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=5669B79E.4000906@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.