From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 220740] Host crash when do PF passthrough to KVM guest with some devices
Date: Mon, 03 Nov 2025 23:47:46 +0000 [thread overview]
Message-ID: <bug-220740-28872-aeAd0AKUgz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220740-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220740
Alex Williamson (alex.l.williamson@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alex.l.williamson@gmail.com
| |, ramesh.thomas@intel.com
--- Comment #2 from Alex Williamson (alex.l.williamson@gmail.com) ---
(In reply to Chen, Fan from comment #1)
> I reproduced this issue on SPR, GNR, SRF, CWF.
Were there platforms that did not reproduce?
> If we disable "PCIE Error Enabling" in BIOS, host will not crash.
>
> After bisecting, the first bad commit is:
> commit 2b938e3db335e3670475e31a722c2bee34748c5a (HEAD)
...
> --- a/drivers/vfio/pci/vfio_pci_rdwr.c
> +++ b/drivers/vfio/pci/vfio_pci_rdwr.c
> @@ -16,6 +16,7 @@
> #include <linux/io.h>
> #include <linux/vfio.h>
> #include <linux/vgaarb.h>
> +#include <linux/io-64-nonatomic-lo-hi.h>
>
> #include "vfio_pci_priv.h"
Theoretically this would only define non-atomic ioread64 and iowrite64 support
on a host that doesn't already have native support for these. Any 64-bit
x86_64 host should already define ioread/write64, so no change in behavior is
expected or intended. Can you provide the kernel .config and compiler
information?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-11-03 23:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 9:12 [Bug 220740] New: Host crash when do PF passthrough to KVM guest with some devices bugzilla-daemon
2025-11-03 9:17 ` [Bug 220740] " bugzilla-daemon
2025-11-03 23:47 ` bugzilla-daemon [this message]
2025-11-04 5:48 ` bugzilla-daemon
2025-11-04 5:53 ` bugzilla-daemon
2025-11-05 0:03 ` bugzilla-daemon
2025-12-09 2:54 ` Tian, Kevin
2025-11-05 4:06 ` bugzilla-daemon
2025-11-05 8:12 ` bugzilla-daemon
2025-12-09 2:54 ` 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-220740-28872-aeAd0AKUgz@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).