From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] kvm: apply VM_READ/VM_WRITE checks to all VMA types
Date: Tue, 4 Aug 2026 06:11:43 -0700 [thread overview]
Message-ID: <anHlD0E0RhIub00d@google.com> (raw)
In-Reply-To: <CABgObfYZvs6rZKSk_Ym=L-vxLHY6WLoo2dL3NneabbUqvZxaDQ@mail.gmail.com>
On Tue, Aug 04, 2026, Paolo Bonzini wrote:
> On Tue, Aug 4, 2026 at 12:40 AM Sean Christopherson <seanjc@google.com> wrote:
> > > > But the issue Sashiko reported is just saying that KVM sometimes does what I'm
> > > > saying KVM should do all the time: return -EFAULT. Or did I misunderstand that
> > > > one too? :-)
> > >
> > > Yes, that's correct. My point is I'd rather not introduce other changes to
> > > the !VM_WRITE case in stable releases.
> >
> > Yeah, agreed. But what I don't understand is why this would be sent to stable@
> > in the first place.
>
> Because the patch
> https://lore.kernel.org/kvm/20260731160514.1101989-1-pbonzini@redhat.com/T/
> needs to be sent to stable@, and this one fixes a problem in that
> other patch. So this one needs to come first.
Oooh, that makes sense. Thanks for being patient.
prev parent reply other threads:[~2026-08-04 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 17:58 [PATCH] kvm: apply VM_READ/VM_WRITE checks to all VMA types Paolo Bonzini
2026-07-31 18:46 ` Sean Christopherson
2026-08-03 5:54 ` Paolo Bonzini
2026-08-03 13:40 ` Sean Christopherson
2026-08-03 17:17 ` Paolo Bonzini
2026-08-03 22:40 ` Sean Christopherson
2026-08-04 7:43 ` Paolo Bonzini
2026-08-04 13:11 ` 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=anHlD0E0RhIub00d@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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