From: Salvatore Bonaccorso <carnil@debian.org>
To: Sean Christopherson <seanjc@google.com>, 1135235-done@bugs.debian.org
Cc: Maximilian Senftleben <kernel@0in.de>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Bug#1135235: linux-image-6.19.13+deb14-amd64: Reoccuring host crash "Invalid SPTE change" with gaming win kvm/qemu guest and device passthrough
Date: Thu, 25 Jun 2026 22:24:36 +0200 [thread overview]
Message-ID: <aj2OhGJreZWxlBKU@eldamar.lan> (raw)
In-Reply-To: <aj1NRsUIVQRGBqM1@google.com>
Source: linux
Source-Version: 7.0.10-1
On Thu, Jun 25, 2026 at 03:46:14PM +0000, Sean Christopherson wrote:
> +lists to capture this for posterity
>
> On Wed, Jun 24, 2026, Maximilian Senftleben wrote:
> > I tried a 7.0.10 with KASAN for several days, and now I am running
> > 7.0.12+deb14.1-amd64 since a couple of days, and at least so far I was not
> > able to reproduce my issue, i.e. I had no crash so far.
>
> That, and the fact that 7.0.7 was fine, strongly suggests a broken fix got
> backported and landed in 7.0.8 or 7.0.9, and then a fix-for-the-fix landed in
> 7.10. There aren't any KVM commits of interest anywhere in that range, which
> supports my theory that KVM is an innocent bystander that ran afoul of memory
> corruption due to a bug elsewhere in the kernel.
>
> Unless you want to bisect to figure out exactly what commit broken things, and
> what commit fixed things, I think it makes sense to consider this resolved unless
> the problem occurs on a 7.0.10+ kernel.
Ack, I'm marking this as fixed with 7.0.10 based version in Debian then.
Regards,
Salvatore
prev parent reply other threads:[~2026-06-25 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <177749023441.304242.8022456530166067549.reportbug@mspc2024debian.lan>
2026-05-17 13:24 ` Bug#1135235: linux-image-6.19.13+deb14-amd64: Reoccuring host crash "Invalid SPTE change" with gaming win kvm/qemu guest and device passthrough Salvatore Bonaccorso
2026-05-17 13:28 ` Paolo Bonzini
2026-05-18 13:43 ` Sean Christopherson
[not found] ` <db210e1d-0d3b-4501-89c5-de7d7de66b03@0in.de>
[not found] ` <aiNCq17MbKfs3hGy@google.com>
[not found] ` <0c183f0f-f23d-45ce-af22-a1f936b9bf2c@0in.de>
2026-06-25 15:46 ` Sean Christopherson
2026-06-25 20:24 ` Salvatore Bonaccorso [this message]
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=aj2OhGJreZWxlBKU@eldamar.lan \
--to=carnil@debian.org \
--cc=1135235-done@bugs.debian.org \
--cc=kernel@0in.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.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 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.