All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 197951] QEMU/KVM & VFIO & PCI passthru with Windows 10 x64 guest: memory access intermittently causes CRITICAL_STRUCTURE_CORRUPTION BSOD unless swap is disabled on host, since 4.12.13
Date: Mon, 04 Dec 2017 08:49:54 +0000	[thread overview]
Message-ID: <bug-197951-28872-ywIQYxqIpX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197951-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=197951

--- Comment #6 from Ladi Prosek (lprosek@redhat.com) ---
I have seen this crash on a Windows 10 x64 guest *without* any kind of device
assignment. Didn't keep track of exact kernel versions but it was Fedora 26,
very likely 4.12.*.

If you've been able to build a kernel where this happens for you, try
cherry-picking:

commit a2b7861bb33b2538420bb5d8554153484d3f961f                       
Author: Boqun Feng <boqun.feng@gmail.com>                             
Date:   Tue Oct 3 21:36:51 2017 +0800                                 

    kvm/x86: Avoid async PF preempting the kernel incorrectly         

    Currently, in PREEMPT_COUNT=n kernel, kvm_async_pf_task_wait() could call
    schedule() to reschedule in some cases.  This could result in     
    accidentally ending the current RCU read-side critical section early,    
    causing random memory corruption in the guest, or otherwise preempting   
    the currently running task inside between preempt_disable and     
    preempt_enable.                


Keywords: "PF" (since the report mentions swap), "random memory corruption in
the guest"

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2017-12-04  8:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 21:19 [Bug 197951] New: QEMU/KVM & VFIO & PCI passthru with Windows 10 x64 guest: memory access intermittently causes CRITICAL_STRUCTURE_CORRUPTION BSOD unless swap is disabled on host, since 4.12.13 bugzilla-daemon
2017-11-21 21:23 ` [Bug 197951] " bugzilla-daemon
2017-11-21 21:32 ` bugzilla-daemon
2017-11-21 21:45 ` bugzilla-daemon
2017-11-30  9:41 ` bugzilla-daemon
2017-11-30 17:45 ` bugzilla-daemon
2017-12-04  8:49 ` bugzilla-daemon [this message]
2017-12-04  9:49 ` bugzilla-daemon
2017-12-04 11:58 ` bugzilla-daemon
2017-12-04 12:32 ` bugzilla-daemon
2017-12-04 13:42 ` bugzilla-daemon
2017-12-04 19:28 ` bugzilla-daemon
2017-12-05  5:52 ` bugzilla-daemon
2017-12-05  8:15 ` bugzilla-daemon
2017-12-05  9:22 ` bugzilla-daemon
2017-12-05 10:04 ` bugzilla-daemon
2017-12-14  7:57 ` bugzilla-daemon

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=bug-197951-28872-ywIQYxqIpX@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@kernel.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.