From: punixcorn <ohyunwoods663@gmail.com>
To: seanjc@google.com, pbonzini@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
punixcorn <ohyunwoods663@gmail.com>
Subject: Re: [BUG] KVM: NULL pointer dereference in kvm_tdp_mmu_map under memory pressure
Date: Wed, 8 Apr 2026 18:43:32 +0000 [thread overview]
Message-ID: <20260408184332.187482-1-ohyunwoods663@gmail.com> (raw)
In-Reply-To: <202604081633.sean.christopherson@intel.com>
To be honest, it could be days. The original crash happened only once
in a month of heavy use, though my system has been hitting 100% RAM
usage frequently.
I suspect a specific transition-like a guest memory zap during high
host contention-is the trigger. I am currently trying to reproduce
this by scripting a loop that reloads the guest project (Android emulator)
while the host is under heavy memory load, as that was the environment
when the crash occurred.
I’ll keep the current debug patch running. If I can't catch it within
the next 48 hours, I’d be very interested in that more elaborate
debug patch you mentioned to help track the SPTE lifecycle more
closely.
Signed-off-by: punixcorn <ohyunwoods663@gmail.com>
next parent reply other threads:[~2026-04-08 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202604081633.sean.christopherson@intel.com>
2026-04-08 18:43 ` punixcorn [this message]
2026-04-13 21:47 ` [BUG] KVM: NULL pointer dereference in kvm_tdp_mmu_map under memory pressure Sean Christopherson
[not found] <202604081418.sean.christopherson@intel.com>
2026-04-08 15:36 ` punixcorn
2026-04-08 16:33 ` Sean Christopherson
2026-04-08 10:29 punixcorn
2026-04-08 11:21 ` punixcorn
2026-04-08 14:18 ` Sean Christopherson
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=20260408184332.187482-1-ohyunwoods663@gmail.com \
--to=ohyunwoods663@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox