All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Nicolin Chen <nicolinc@nvidia.com>,
	"joro@8bytes.org" <joro@8bytes.org>,
	"will@kernel.org" <will@kernel.org>,
	"robin.murphy@arm.com" <robin.murphy@arm.com>,
	"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	"shuah@kernel.org" <shuah@kernel.org>,
	"Liu, Yi L" <yi.l.liu@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"baolu.lu@linux.intel.com" <baolu.lu@linux.intel.com>
Subject: Re: [PATCH v2 10/10] vfio: Do not allow !ops->dma_unmap in vfio_pin/unpin_pages()
Date: Thu, 9 Feb 2023 09:26:15 -0400	[thread overview]
Message-ID: <Y+T0d9ox3KnqMDIL@nvidia.com> (raw)
In-Reply-To: <BN9PR11MB527687E27FC35CD842E4EA7B8CD99@BN9PR11MB5276.namprd11.prod.outlook.com>

On Thu, Feb 09, 2023 at 04:10:04AM +0000, Tian, Kevin wrote:
> > From: Nicolin Chen <nicolinc@nvidia.com>
> > Sent: Wednesday, February 8, 2023 5:18 AM
> > 
> > A driver that doesn't implement ops->dma_unmap shouldn't be allowed to
> > do
> > vfio_pin/unpin_pages(), though it can use vfio_dma_rw() to access an iova
> > range. Deny !ops->dma_unmap cases in vfio_pin/unpin_pages().
> > 
> > Suggested-by: Kevin Tian <kevin.tian@intel.com>
> > Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>
> > ---
> >  drivers/vfio/vfio_main.c | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/drivers/vfio/vfio_main.c b/drivers/vfio/vfio_main.c
> > index 8559c3dfb335..c7f3251ad6e5 100644
> > --- a/drivers/vfio/vfio_main.c
> > +++ b/drivers/vfio/vfio_main.c
> > @@ -1543,6 +1543,8 @@ int vfio_pin_pages(struct vfio_device *device,
> > dma_addr_t iova,
> > 
> >  		if (iova > ULONG_MAX)
> >  			return -EINVAL;
> > +		if (!device->ops->dma_unmap)
> > +			return -EINVAL;
> >  		/*
> >  		 * VFIO ignores the sub page offset, npages is from the start
> > of
> >  		 * a PAGE_SIZE chunk of IOVA. The caller is expected to
> > recover
> > @@ -1580,6 +1582,8 @@ void vfio_unpin_pages(struct vfio_device *device,
> > dma_addr_t iova, int npage)
> >  	if (device->iommufd_access) {
> >  		if (WARN_ON(iova > ULONG_MAX))
> >  			return;
> > +		if (!device->ops->dma_unmap)
> > +			return;
> 
> IMHO this restriction applies to both iommufd and legacy container.

Yeah that makes sense

Jason

  reply	other threads:[~2023-02-09 13:26 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 21:17 [PATCH v2 00/10] Add IO page table replacement support Nicolin Chen
2023-02-07 21:17 ` [PATCH v2 01/10] iommu: Move dev_iommu_ops() to private header Nicolin Chen
2023-02-09  2:49   ` Tian, Kevin
2023-02-07 21:17 ` [PATCH v2 02/10] iommu: Introduce a new iommu_group_replace_domain() API Nicolin Chen
2023-02-09  2:55   ` Tian, Kevin
2023-02-09 13:23     ` Jason Gunthorpe
2023-02-10  1:34       ` Tian, Kevin
2023-02-10 23:51   ` Alex Williamson
2023-02-11  0:44     ` Jason Gunthorpe
2023-02-13  2:24       ` Tian, Kevin
2023-02-13  8:34         ` Baolu Lu
2023-02-13 14:45         ` Jason Gunthorpe
2023-02-14  3:29           ` Tian, Kevin
2023-02-15  6:10   ` Tian, Kevin
2023-02-15 12:52     ` Jason Gunthorpe
2023-02-22  2:11       ` Tian, Kevin
2023-02-24  0:57         ` Jason Gunthorpe
2023-02-24  8:07           ` Tian, Kevin
2023-02-07 21:17 ` [PATCH v2 03/10] iommufd: Create access in vfio_iommufd_emulated_bind() Nicolin Chen
2023-02-09  2:56   ` Tian, Kevin
2023-02-09 16:15     ` Nicolin Chen
2023-02-09 18:58   ` Eric Farman
2023-02-09 19:54     ` Nicolin Chen
2023-02-07 21:17 ` [PATCH v2 04/10] iommufd/selftest: Add IOMMU_TEST_OP_ACCESS_SET_IOAS coverage Nicolin Chen
2023-02-09  2:59   ` Tian, Kevin
2023-02-07 21:17 ` [PATCH v2 05/10] iommufd: Add replace support in iommufd_access_set_ioas() Nicolin Chen
2023-02-09  3:13   ` Tian, Kevin
2023-02-09 20:28     ` Nicolin Chen
2023-02-09 20:49       ` Jason Gunthorpe
2023-02-09 22:18         ` Nicolin Chen
2023-02-07 21:17 ` [PATCH v2 06/10] iommufd/selftest: Add coverage for access->ioas replacement Nicolin Chen
2023-02-07 21:17 ` [PATCH v2 07/10] iommufd/device: Make hwpt_list list_add/del symmetric Nicolin Chen
2023-02-09  3:23   ` Tian, Kevin
2023-02-09 13:24     ` Jason Gunthorpe
2023-02-10  1:46       ` Tian, Kevin
2023-02-10 21:17         ` Jason Gunthorpe
2023-02-13  2:12           ` Tian, Kevin
2023-02-07 21:18 ` [PATCH v2 08/10] iommufd/device: Use iommu_group_replace_domain() Nicolin Chen
2023-02-08  8:08   ` Liu, Yi L
2023-02-09 20:55     ` Nicolin Chen
2023-02-08  8:12   ` Liu, Yi L
2023-02-09 20:56     ` Nicolin Chen
2023-02-09  4:00   ` Tian, Kevin
2023-02-09 21:13     ` Nicolin Chen
2023-02-10  0:01       ` Jason Gunthorpe
2023-02-10 20:50         ` Nicolin Chen
2023-02-10  2:11       ` Tian, Kevin
2023-02-11  0:10         ` Nicolin Chen
2023-02-13  2:34           ` Tian, Kevin
2023-02-13  7:48             ` Nicolin Chen
2023-02-13  8:27               ` Tian, Kevin
2023-02-13 14:49               ` Jason Gunthorpe
2023-02-14 10:54                 ` Nicolin Chen
2023-02-15  1:37                   ` Tian, Kevin
2023-02-15  1:58                     ` Nicolin Chen
2023-02-15  2:15                       ` Tian, Kevin
2023-02-15  7:15                         ` Nicolin Chen
2023-02-15  7:24                           ` Tian, Kevin
2023-02-15 12:51                           ` Jason Gunthorpe
2023-02-14 10:59         ` Nicolin Chen
2023-02-15  1:38           ` Tian, Kevin
2023-02-15  7:16             ` Nicolin Chen
2023-02-07 21:18 ` [PATCH v2 09/10] vfio: Support IO page table replacement Nicolin Chen
2023-02-09  4:06   ` Tian, Kevin
2023-02-07 21:18 ` [PATCH v2 10/10] vfio: Do not allow !ops->dma_unmap in vfio_pin/unpin_pages() Nicolin Chen
2023-02-09  4:10   ` Tian, Kevin
2023-02-09 13:26     ` Jason Gunthorpe [this message]
2023-02-09 16:19       ` Nicolin Chen
2023-02-09  2:50 ` [PATCH v2 00/10] Add IO page table replacement support Tian, Kevin
2023-02-09 16:13   ` Nicolin Chen
2023-02-10  1:34     ` Tian, Kevin

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=Y+T0d9ox3KnqMDIL@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=shuah@kernel.org \
    --cc=will@kernel.org \
    --cc=yi.l.liu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.