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 15:36:50 +0000 [thread overview]
Message-ID: <20260408153650.34484-1-ohyunwoods663@gmail.com> (raw)
In-Reply-To: <202604081418.sean.christopherson@intel.com>
Hi Sean,
I attempted to trigger your debug patch via fault injection (zeroing
page_private on the allocated sp before it's linked), but the resulting
logs aren't meaningful -- every captured entry shows spte =
8000000000000000, a non-present SPTE, which doesn't reflect the real
crash scenario where the SPTE is present but page_private returns 0.
So I'm not sending those.
Natural reproduction is rare and I haven't caught it yet
with your patch applied.
Given that, what would you recommend as a next step? Would lockdep,
KASAN, or RCU debugging (CONFIG_PROVE_RCU) be worth enabling to catch
the violation when it happens naturally?
Environment:
- CPU: 13th Gen Intel(R) Core(TM) i5-13420H (12) @ 4.60 GHz
- RAM: 16GB (15Gi usable, 16Gi swap)
- OS: Arch Linux
- Kernel: 6.19.10-dirty #1 SMP PREEMPT_DYNAMIC Wed Apr 8 06:08:08 GMT 2026 x86_64
- /proc/cpuinfo: https://pastebin.com/pwvNYsCu
- .config: https://pastebin.com/z4fVZENs
The crash occurs while running an Android emulator (QEMU) under host
memory pressure.
Signed-off-by: punixcorn <ohyunwoods663@gmail.com>
next parent reply other threads:[~2026-04-08 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202604081418.sean.christopherson@intel.com>
2026-04-08 15:36 ` punixcorn [this message]
2026-04-08 16:33 ` Sean Christopherson
[not found] <202604081633.sean.christopherson@intel.com>
2026-04-08 18:43 ` punixcorn
2026-04-13 21:47 ` 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=20260408153650.34484-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
all inboxes | Powered by JetHome®