Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Jeongjun Park <aha310510@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	David Woodhouse <dwmw@amazon.co.uk>,
	 Paul Durrant <pdurrant@amazon.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 syzbot+0948c82180d475ad24e2@syzkaller.appspotmail.com
Subject: Re: [PATCH] KVM: pfncache: track HVA invalidations for HVA-based caches
Date: Mon, 27 Jul 2026 10:25:30 -0700	[thread overview]
Message-ID: <ameUih-zuAoR_pnC@google.com> (raw)
In-Reply-To: <CAO9qdTH7LCO-N9brn95fq49muA5Ud=kixJUYC4pwDJ9eL-qE7A@mail.gmail.com>

On Mon, Jul 27, 2026, Jeongjun Park wrote:
> Hi,
> 
> Sean Christopherson <seanjc@google.com> wrote:
> >
> > On Wed, May 20, 2026, Jeongjun Park wrote:
> > > HVA-based gfn_to_pfn caches are not necessarily backed by a KVM memslot.
> > > When an MMU notifier invalidation targets such an HVA, KVM's global
> [....]
> > >
> > > Reported-by: syzbot+0948c82180d475ad24e2@syzkaller.appspotmail.com
> > > Closes: https://lore.kernel.org/all/6a0c5f2c.a00a0220.2c7954.0000.GAE@google.com
> >
> > Given that there's no reproducer, how did you test this?
> >
> 
> For some unknown reason, repro was not generated in syzbot, so I analyzed
> the KASAN logs separately to predict a sequence similar to the race
> sequence you suggested, and then wrote the repro code myself to test it.

Can you provide the reproducer?  That would be super helpful for reviewing and
iterating on this fix, and probably as a regression test for future changes as
well.

Thanks!

      reply	other threads:[~2026-07-27 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 11:13 [PATCH] KVM: pfncache: track HVA invalidations for HVA-based caches Jeongjun Park
2026-06-25 21:45 ` Sean Christopherson
2026-07-26 21:31   ` Jeongjun Park
2026-07-27 17:25     ` Sean Christopherson [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=ameUih-zuAoR_pnC@google.com \
    --to=seanjc@google.com \
    --cc=aha310510@gmail.com \
    --cc=dwmw@amazon.co.uk \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pdurrant@amazon.com \
    --cc=syzbot+0948c82180d475ad24e2@syzkaller.appspotmail.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