From: Paul Mackerras <paulus@ozlabs.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: linuxppc-dev@lists.ozlabs.org,
David Gibson <david@gibson.dropbear.id.au>,
kvm-ppc@vger.kernel.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Alex Williamson <alex.williamson@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH kernel v7 0/2] KVM: PPC: Check if IOMMU page is contained in the pinned physical page
Date: Wed, 18 Jul 2018 16:28:31 +1000 [thread overview]
Message-ID: <20180718062831.GA27453@fergus> (raw)
In-Reply-To: <20180717071913.2167-1-aik@ozlabs.ru>
On Tue, Jul 17, 2018 at 05:19:11PM +1000, Alexey Kardashevskiy wrote:
> This is to improve page boundaries checking and should probably
> be cc:stable. I came accross this while debugging nvlink2 passthrough
> but the lack of checking might be exploited by the existing userspace.
>
> The get_user_pages() comment says it should be "phased out" but the only
> alternative seems to be get_user_pages_longterm(), should that be used
> instead (this is longterm reference elevation, however it is not DAX,
> whatever this implies)? get_user_pages_remote() seems unnecessarily
> complicated because of @locked.
>
>
> Changes:
> v7:
> * 2/2: do not fail if pte is not found, fall back to the default case instead
>
> v6:
> * 2/2: read pageshift from pte
>
> v5:
> * 2/2: changed compound pages handling
>
> v4:
> * 2/2: implemented less strict but still safe max pageshift as David suggested
>
> v3:
> * enforced huge pages not to cross preregistered chunk boundaries
>
> v2:
> * 2/2: explicitly check for compound pages before calling compound_order()
>
>
> This is based on sha1
> 9d3cce1 Linus Torvalds "Linux 4.18-rc5".
>
> Please comment. Thanks.
>
>
>
> Alexey Kardashevskiy (2):
> vfio/spapr: Use IOMMU pageshift rather than pagesize
> KVM: PPC: Check if IOMMU page is contained in the pinned physical page
>
> arch/powerpc/include/asm/mmu_context.h | 4 ++--
> arch/powerpc/kvm/book3s_64_vio.c | 2 +-
> arch/powerpc/kvm/book3s_64_vio_hv.c | 6 ++++--
> arch/powerpc/mm/mmu_context_iommu.c | 37 ++++++++++++++++++++++++++++++++--
> drivers/vfio/vfio_iommu_spapr_tce.c | 10 ++++-----
> 5 files changed, 47 insertions(+), 12 deletions(-)
Thanks, series applied to my kvm-ppc-next branch.
Paul.
prev parent reply other threads:[~2018-07-18 6:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 7:19 [PATCH kernel v7 0/2] KVM: PPC: Check if IOMMU page is contained in the pinned physical page Alexey Kardashevskiy
2018-07-17 7:19 ` [PATCH kernel v7 1/2] vfio/spapr: Use IOMMU pageshift rather than pagesize Alexey Kardashevskiy
2018-07-19 6:06 ` [kernel, v7, " Michael Ellerman
2018-07-20 3:06 ` [kernel,v7,1/2] " Paul Mackerras
2018-07-17 7:19 ` [PATCH kernel v7 2/2] KVM: PPC: Check if IOMMU page is contained in the pinned physical page Alexey Kardashevskiy
2018-07-18 2:11 ` David Gibson
2018-07-19 6:06 ` [kernel, v7, " Michael Ellerman
2018-07-18 6:28 ` Paul Mackerras [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=20180718062831.GA27453@fergus \
--to=paulus@ozlabs.org \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).