From: Borislav Petkov <bp@alien8.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nikola Ciprich <nikola.ciprich@linuxbox.cz>,
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: Thu, 15 Oct 2026 20:12:42 -0700 [thread overview]
Message-ID: <20261016031242.GDatGWKo98YSOhEOOn@fat_crate.local> (raw)
In-Reply-To: <20261015172820.7961d2c0def74d41cc6c4b0c@linux-foundation.org>
On Thu, Oct 15, 2026 at 05:28:20PM -0700, Andrew Morton wrote:
> fwiw, I fed a lot of tokens into $LLM and it suggests that 55780d8a1dcc
> fixed this.
>
> If that sounds sane then testing 55780d8a1dcc on that 6.18.x kernel
> would be useful.
Hmm, dunno if that LLM sent you into the weeds. Because I ain't no virt guy
but if vmcb01 and vmcb02 and "L2" in that commit message refer to nested virt,
I don't think any of those crash dumps do nested virtualization.
But hey, what do I know... :)
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-10-16 3:13 UTC|newest]
Thread overview: 42+ 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 [this message]
2026-10-16 4:18 ` Andrew Morton
2026-10-16 5:49 ` Borislav Petkov
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=20261016031242.GDatGWKo98YSOhEOOn@fat_crate.local \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--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=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®