From: Andrew Morton <akpm@linux-foundation.org>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: Sean Christopherson <seanjc@google.com>,
Borislav Petkov <bp@alien8.de>,
David Laight <david.laight.linux@gmail.com>,
Rik van Riel <riel@surriel.com>,
ljs@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
david@kernel.org, Mike Rapoport <rppt@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Pedro Falcato <pfalcato@suse.de>,
Kiryl Shutsemau <kas@kernel.org>,
luizcap@redhat.com, pbonzini@redhat.com,
Tal Zussman <tz2294@columbia.edu>,
Matt Fleming <matt@readmodwrite.com>
Subject: Re: hunting memory corruption bug in 6.18.x
Date: Sun, 18 Oct 2026 20:15:38 -0700 [thread overview]
Message-ID: <20261018201538.d0957878f378a9821852836f@linux-foundation.org> (raw)
In-Reply-To: <atT5TYyLapHO5ZoX@pcnci.linuxbox.cz>
On Sun, 18 Oct 2026 18:52:29 +0200 Nikola Ciprich <nikola.ciprich@linuxbox.cz> wrote:
>
> Hello Sean (and others),
>
> I think I've finally found the (at least) one missing piece needed to reproduce
> this. At first I wasn't paying much attention to nested virtualization, because
> we don't use it much (or so I thought), but I was still wondering why
> why all of this seems to be tied to Windows guests. So I dug into advanced
> Windows security features and found out that newer Windows versions use
> something called Virtualization-Based Security (VBS), which relies on
> exactly that: SVM/VMX, i.e. nested virtualization. (I'm not a Windows guy,
> so excuse my ignorance here.)
Well we initially thought that nested virtualization was not involved.
It it indeed is in the picture then it might have been 55780d8a1dcc
which unknowingly fixed this.
Are you able to test that commit on the 6.18 kernel?
next prev parent reply other threads:[~2026-10-19 3:15 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 8:48 Nikola Ciprich
2026-09-25 10:05 ` Lorenzo Stoakes (ARM)
2026-09-25 12:13 ` Lorenzo Stoakes (ARM)
2026-09-26 5:58 ` Nikola Ciprich
2026-09-26 9:32 ` Lorenzo Stoakes (ARM)
2026-09-28 9:05 ` Nikola Ciprich
2026-09-29 19:11 ` Nikola Ciprich
2026-09-30 9:07 ` Lorenzo Stoakes (ARM)
2026-09-30 18:40 ` Nikola Ciprich
2026-10-01 19:40 ` Nikola Ciprich
2026-10-01 22:21 ` David Laight
2026-10-02 9:50 ` Lorenzo Stoakes (ARM)
2026-10-02 14:55 ` Nikola Ciprich
2026-10-02 19:27 ` Lorenzo Stoakes (ARM)
2026-10-04 18:40 ` Nikola Ciprich
2026-10-05 11:25 ` Rik van Riel
2026-10-05 19:02 ` Nikola Ciprich
[not found] ` <20261005132113.43548696@pumpkin>
2026-10-05 19:25 ` Nikola Ciprich
2026-10-08 12:29 ` Nikola Ciprich
2026-10-08 18:23 ` Borislav Petkov
2026-10-08 20:48 ` Nikola Ciprich
2026-10-09 8:00 ` David Laight
2026-10-12 11:43 ` Nikola Ciprich
2026-10-14 23:53 ` Borislav Petkov
2026-10-15 9:10 ` Nikola Ciprich
2026-10-15 22:11 ` Borislav Petkov
2026-10-14 23:57 ` Borislav Petkov
2026-10-15 9:14 ` Nikola Ciprich
2026-10-15 22:15 ` Borislav Petkov
2026-10-16 0:28 ` Andrew Morton
2026-10-16 3:12 ` Borislav Petkov
2026-10-16 4:18 ` Andrew Morton
2026-10-16 5:49 ` Borislav Petkov
2026-10-16 15:16 ` Sean Christopherson
2026-10-18 16:52 ` Nikola Ciprich
2026-10-19 3:15 ` Andrew Morton [this message]
2026-10-19 8:40 ` Nikola Ciprich
2026-10-19 15:22 ` Nikola Ciprich
2026-10-19 15:35 ` Andrew Morton
2026-10-19 16:38 ` Lorenzo Stoakes (ARM)
2026-10-02 22:02 ` Borislav Petkov
2026-10-04 18:45 ` Nikola Ciprich
2026-10-05 10:58 ` Rik van Riel
2026-10-05 18:05 ` Nikola Ciprich
2026-09-26 16:02 ` Luiz Capitulino
2026-09-28 8:47 ` Nikola Ciprich
2026-10-04 22:20 ` Rik van Riel
2026-10-05 9:31 ` Nikola Ciprich
2026-10-05 8:31 ` Lance Yang
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=20261018201538.d0957878f378a9821852836f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david.laight.linux@gmail.com \
--cc=david@kernel.org \
--cc=kas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=luizcap@redhat.com \
--cc=matt@readmodwrite.com \
--cc=nikola.ciprich@linuxbox.cz \
--cc=pbonzini@redhat.com \
--cc=pfalcato@suse.de \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=tz2294@columbia.edu \
/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
all inboxes | Powered by JetHome®