From: Paolo Bonzini <pbonzini@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, jgg@ziepe.ca,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
dan.j.williams@intel.com, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH 1/2] mm: provide a sane PTE walking API for modules
Date: Tue, 9 Feb 2021 10:19:33 +0100 [thread overview]
Message-ID: <d238b495-dbae-1bc4-3397-5bceadfddb7e@redhat.com> (raw)
In-Reply-To: <20210209081408.GA1703597@infradead.org>
On 09/02/21 09:14, Christoph Hellwig wrote:
> On Mon, Feb 08, 2021 at 07:18:56PM +0100, Paolo Bonzini wrote:
>> Fair enough. I would expect that pretty much everyone using follow_pfn will
>> at least want to switch to this one (as it's less bad and not impossible to
>> use correctly), but I'll squash this in:
>
>
> Daniel looked into them, so he may correct me, but the other follow_pfn
> users and their destiny are:
>
> - SGX, which is not modular and I think I just saw a patch to kill them
> - v4l videobuf and frame vector: I think those are going away
> entirely as they implement a rather broken pre-dmabuf P2P scheme
> - vfio: should use MMU notifiers eventually
Yes, I'm thinking mostly of vfio, which could use follow_pte as a
short-term fix for just the missing permission check.
There's also s390 PCI, which is also not modular.
Paolo
> Daniel, what happened to your follow_pfn series?
next prev parent reply other threads:[~2021-02-09 9:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 10:32 [PATCH 0/2] KVM: do not assume PTE is writable after follow_pfn Paolo Bonzini
2021-02-05 10:32 ` [PATCH 1/2] mm: provide a sane PTE walking API for modules Paolo Bonzini
2021-02-05 13:49 ` Jason Gunthorpe
2021-02-08 17:39 ` Christoph Hellwig
2021-02-08 18:18 ` Paolo Bonzini
2021-02-09 8:14 ` Christoph Hellwig
2021-02-09 9:19 ` Paolo Bonzini [this message]
2021-02-05 10:32 ` [PATCH 2/2] KVM: do not assume PTE is writable after follow_pfn Paolo Bonzini
2021-02-05 15:43 ` kernel test robot
2021-02-05 17:41 ` kernel test robot
2021-02-05 18:14 ` [PATCH 0/2] " Peter Xu
2021-02-08 18:51 ` Jason Gunthorpe
2021-02-08 22:02 ` Peter Xu
2021-02-08 23:26 ` Jason Gunthorpe
2021-02-09 0:23 ` Peter Xu
2021-02-09 8:19 ` Christoph Hellwig
2021-02-09 10:02 ` Joao Martins
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=d238b495-dbae-1bc4-3397-5bceadfddb7e@redhat.com \
--to=pbonzini@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=daniel@ffwll.ch \
--cc=hch@infradead.org \
--cc=jgg@ziepe.ca \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).