Re: [PATCH v2 0/6] mm, drm: fix interaction of .pfn_mkwrite() with fixup_user_fault()

From: Paolo Bonzini

Date: Tue Oct 27 2026 - 07:07:35 EST


On Mon, Oct 26, 2026 at 2:50 PM Sean Christopherson <seanjc@xxxxxxxxxx> wrote:
> > To sum up:
> >
> > - patches 1-3 introduce the new MM API, and use it in the DRM .fault()
> > callbacks to install writable PTEs in response to write faults
> >
> > - patch 4 is a preparatory fix in KVM, eliminating inconsistencies in the
> > handling of !VM_READ and !VM_WRITE VMAs; these would return different
> > error codes for a !VM_WRITE VMA depending on whether the PTE happens
> > to be mapped (but with wrong permissions). This needs to be here
> > because the next patch would introduce even more inconsistencies.
> >
> > - patch 5 moves the check for writable PTEs from follow_pfnmap_start()'s
> > callers to the function itself
> >
> > - finally, patch 6 is a KVM addendum that will have to wait until
> > the next merge window; it removes yet another inconsistency in
> > KVM's handling of !VM_WRITE but is technically userspace-visible,
> > and therefore it shouldn't be included in stable kernel releases
> > unlike the rest.
>
> What happened to this series? It seemed liked something semi-urgent, but AFAICT
> it got silently dropped?

It ballooned a bit and getting acks from everyone involved is hard...
Either I or Sergio will get back to it.

Paolo