From: "Zengtao (B)" <prime.zeng@hisilicon.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>
Cc: Peter Xu <peterx@redhat.com>, Cornelia Huck <cohuck@redhat.com>,
"Kevin Tian" <kevin.tian@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Giovanni Cabiddu <giovanni.cabiddu@intel.com>,
Michel Lespinasse <walken@google.com>,
Jann Horn <jannh@google.com>, Max Gurtovoy <mgurtovoy@nvidia.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>
Subject: 答复: [PATCH] vfio/pci: make the vfio_pci_mmap_fault reentrant
Date: Thu, 11 Mar 2021 03:32:35 +0000 [thread overview]
Message-ID: <70e217159188451b8b0a7c88dd15cb44@hisilicon.com> (raw)
In-Reply-To: <20210309230837.394cb101@x1.home.shazbot.org>
Hi Alex:
> -----邮件原件-----
> 发件人: Alex Williamson [mailto:alex.williamson@redhat.com]
> 发送时间: 2021年3月10日 14:09
> 收件人: Jason Gunthorpe <jgg@nvidia.com>
> 抄送: Peter Xu <peterx@redhat.com>; Zengtao (B) <prime.zeng@hisilicon.com>;
> Cornelia Huck <cohuck@redhat.com>; Kevin Tian <kevin.tian@intel.com>;
> Andrew Morton <akpm@linux-foundation.org>; Giovanni Cabiddu
> <giovanni.cabiddu@intel.com>; Michel Lespinasse <walken@google.com>; Jann
> Horn <jannh@google.com>; Max Gurtovoy <mgurtovoy@nvidia.com>;
> kvm@vger.kernel.org; linux-kernel@vger.kernel.org; Linuxarm
> <linuxarm@huawei.com>
> 主题: Re: [PATCH] vfio/pci: make the vfio_pci_mmap_fault reentrant
>
> On Tue, 9 Mar 2021 19:41:27 -0400
> Jason Gunthorpe <jgg@nvidia.com> wrote:
>
> > On Tue, Mar 09, 2021 at 12:26:07PM -0700, Alex Williamson wrote:
> >
> > > In the new series, I think the fault handler becomes (untested):
> > >
> > > static vm_fault_t vfio_pci_mmap_fault(struct vm_fault *vmf) {
> > > struct vm_area_struct *vma = vmf->vma;
> > > struct vfio_pci_device *vdev = vma->vm_private_data;
> > > unsigned long base_pfn, pgoff;
> > > vm_fault_t ret = VM_FAULT_SIGBUS;
> > >
> > > if (vfio_pci_bar_vma_to_pfn(vma, &base_pfn))
> > > return ret;
> > >
> > > pgoff = (vmf->address - vma->vm_start) >> PAGE_SHIFT;
> >
> > I don't think this math is completely safe, it needs to parse the
> > vm_pgoff..
> >
> > I'm worried userspace could split/punch/mangle a VMA using
> > munmap/mremap/etc/etc in a way that does update the pg_off but is
> > incompatible with the above.
>
> parsing vm_pgoff is done in:
>
> static int vfio_pci_bar_vma_to_pfn(struct vm_area_struct *vma,
> unsigned long *pfn) {
> struct vfio_pci_device *vdev = vma->vm_private_data;
> struct pci_dev *pdev = vdev->pdev;
> int index;
> u64 pgoff;
>
> index = vma->vm_pgoff >> (VFIO_PCI_OFFSET_SHIFT - PAGE_SHIFT);
>
> if (index >= VFIO_PCI_ROM_REGION_INDEX ||
> !vdev->bar_mmap_supported[index] || !vdev->barmap[index])
> return -EINVAL;
>
> pgoff = vma->vm_pgoff &
> ((1U << (VFIO_PCI_OFFSET_SHIFT - PAGE_SHIFT)) - 1);
>
> *pfn = (pci_resource_start(pdev, index) >> PAGE_SHIFT) + pgoff;
>
> return 0;
> }
>
> But given Peter's concern about faulting individual pages, I think the fault handler
> becomes:
>
> static vm_fault_t vfio_pci_mmap_fault(struct vm_fault *vmf) {
> struct vm_area_struct *vma = vmf->vma;
> struct vfio_pci_device *vdev = vma->vm_private_data;
> unsigned long vaddr, pfn;
> vm_fault_t ret = VM_FAULT_SIGBUS;
>
> if (vfio_pci_bar_vma_to_pfn(vma, &pfn))
> return ret;
>
> down_read(&vdev->memory_lock);
>
> if (__vfio_pci_memory_enabled(vdev)) {
> for (vaddr = vma->vm_start;
> vaddr < vma->vm_end; vaddr += PAGE_SIZE, pfn++) {
One concern here is the performance, since you are doing the mapping for the
whole vma, what about using block mapping if applicable?
> ret = vmf_insert_pfn_prot(vma, vaddr, pfn,
>
> pgprot_decrypted(vma->vm_page_prot));
> if (ret != VM_FAULT_NOPAGE) {
> zap_vma_ptes(vma, vma->vm_start,
> vaddr - vma->vm_start);
> break;
> }
> }
> }
>
> up_read(&vdev->memory_lock);
>
> return ret;
> }
>
> Thanks,
> Alex
next prev parent reply other threads:[~2021-03-11 3:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 11:11 Zeng Tao
2021-03-08 20:21 ` Alex Williamson
2021-03-08 22:56 ` Peter Xu
2021-03-09 3:49 ` 答复: " Zengtao (B)
2021-03-09 12:46 ` Jason Gunthorpe
2021-03-09 15:29 ` Alex Williamson
2021-03-09 16:40 ` Jason Gunthorpe
2021-03-09 18:47 ` Peter Xu
2021-03-09 19:26 ` Alex Williamson
2021-03-09 19:48 ` Peter Xu
2021-03-09 20:11 ` Alex Williamson
2021-03-09 21:00 ` Peter Xu
2021-03-09 21:43 ` Alex Williamson
2021-03-09 19:56 ` Alex Williamson
2021-03-09 23:45 ` Jason Gunthorpe
2021-03-10 6:23 ` Alex Williamson
2021-03-09 23:41 ` Jason Gunthorpe
2021-03-10 6:08 ` Alex Williamson
2021-03-11 3:32 ` Zengtao (B) [this message]
2021-03-08 23:43 ` Jason Gunthorpe
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=70e217159188451b8b0a7c88dd15cb44@hisilicon.com \
--to=prime.zeng@hisilicon.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=giovanni.cabiddu@intel.com \
--cc=jannh@google.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mgurtovoy@nvidia.com \
--cc=peterx@redhat.com \
--cc=walken@google.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
all inboxes | Powered by JetHome®