Re: [RFC v2 2/3] vfio/type1: VFIO_IOMMU_PASID_REQUEST(alloc/free)

Alex Williamson
2019-11-07T22:07:14Z

On Wed, 6 Nov 2019 13:27:26 +0000
"Liu, Yi L" <yi.l.liu@intel.com> wrote:

> > From: Alex Williamson <alex.williamson@redhat.com>
> > Sent: Wednesday, November 6, 2019 7:36 AM
> > To: Liu, Yi L <yi.l.liu@intel.com>
> > Subject: Re: [RFC v2 2/3] vfio/type1: VFIO_IOMMU_PASID_REQUEST(alloc/free)
> >
> > On Thu, 24 Oct 2019 08:26:22 -0400
> > Liu Yi L <yi.l.liu@intel.com> wrote:
> >
> > > This patch adds VFIO_IOMMU_PASID_REQUEST ioctl which aims
> > > to passdown PASID allocation/free request from the virtual
> > > iommu. This is required to get PASID managed in system-wide.
> > >
> > > Cc: Kevin Tian <kevin.tian@intel.com>
> > > Signed-off-by: Liu Yi L <yi.l.liu@intel.com>
> > > Signed-off-by: Yi Sun <yi.y.sun@linux.intel.com>
> > > Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
> > > ---
> > > drivers/vfio/vfio_iommu_type1.c | 114
> > ++++++++++++++++++++++++++++++++++++++++
> > > include/uapi/linux/vfio.h | 25 +++++++++
> > > 2 files changed, 139 insertions(+)
> > >
> > > diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> > > index cd8d3a5..3d73a7d 100644
> > > --- a/drivers/vfio/vfio_iommu_type1.c
> > > +++ b/drivers/vfio/vfio_iommu_type1.c
> > > @@ -2248,6 +2248,83 @@ static int vfio_cache_inv_fn(struct device *dev, void
> > *data)
> > > return iommu_cache_invalidate(dc->domain, dev, &ustruct->info);
> > > }
> > >
> > > +static int vfio_iommu_type1_pasid_alloc(struct vfio_iommu *iommu,
> > > + int min_pasid,
> > > + int max_pasid)
> > > +{
> > > + int ret;
> > > + ioasid_t pasid;
> > > + struct mm_struct *mm = NULL;
> > > +
> > > + mutex_lock(&iommu->lock);
> > > + if (!IS_IOMMU_CAP_DOMAIN_IN_CONTAINER(iommu)) {
> > > + ret = -EINVAL;
> > > + goto out_unlock;
> > > + }
> > > + mm = get_task_mm(current);
> > > + /* Track ioasid allocation owner by mm */
> > > + pasid = ioasid_alloc((struct ioasid_set *)mm, min_pasid,
> > > + max_pasid, NULL);
> >
> > Are we sure we want to tie this to the task mm vs perhaps the
> > vfio_iommu pointer?
>
> Here we want to have a kind of per-VM mark, which can be used to do
> ownership check on whether a pasid is held by a specific VM. This is
> very important to prevent across VM affect. vfio_iommu pointer is
> competent for vfio as vfio is both pasid alloc requester and pasid
> consumer. e.g. vfio requests pasid alloc from ioasid and also it will
> invoke bind_gpasid(). vfio can either check ownership before invoking
> bind_gpasid() or pass vfio_iommu pointer to iommu driver. But in future,
> there may be other modules which are just consumers of pasid. And they
> also want to do ownership check for a pasid. Then, it would be hard for
> them as they are not the pasid alloc requester. So here better to have
> a system wide structure to perform as the per-VM mark. task mm looks
> to be much competent.

Ok, so it's intentional to have a VM-wide token. Elsewhere in the
type1 code (vfio_dma_do_map) we record the task_struct per dma mapping
so that we can get the task mm as needed. Would the task_struct
pointer provide any advantage?

Also, an overall question, this provides userspace with pasid alloc and
free ioctls, (1) what prevents a userspace process from consuming every
available pasid, and (2) if the process exits or crashes without
freeing pasids, how are they recovered aside from a reboot?

> > > + if (pasid == INVALID_IOASID) {
> > > + ret = -ENOSPC;
> > > + goto out_unlock;
> > > + }
> > > + ret = pasid;
> > > +out_unlock:
> > > + mutex_unlock(&iommu->lock);

What does holding this lock protect? That the vfio_iommu remains
backed by an iommu during this operation, even though we don't do
anything to release allocated pasids when that iommu backing is removed?

> > > + if (mm)
> > > + mmput(mm);
> > > + return ret;
> > > +}
> > > +
> > > +static int vfio_iommu_type1_pasid_free(struct vfio_iommu *iommu,
> > > + unsigned int pasid)
> > > +{
> > > + struct mm_struct *mm = NULL;
> > > + void *pdata;
> > > + int ret = 0;
> > > +
> > > + mutex_lock(&iommu->lock);
> > > + if (!IS_IOMMU_CAP_DOMAIN_IN_CONTAINER(iommu)) {
> > > + ret = -EINVAL;
> > > + goto out_unlock;
> > > + }
> > > +
> > > + /**
> > > + * REVISIT:
> > > + * There are two cases free could fail:
> > > + * 1. free pasid by non-owner, we use ioasid_set to track mm, if
> > > + * the set does not match, caller is not permitted to free.
> > > + * 2. free before unbind all devices, we can check if ioasid private
> > > + * data, if data != NULL, then fail to free.
> > > + */
> > > + mm = get_task_mm(current);
> > > + pdata = ioasid_find((struct ioasid_set *)mm, pasid, NULL);
> > > + if (IS_ERR(pdata)) {
> > > + if (pdata == ERR_PTR(-ENOENT))
> > > + pr_err("PASID %u is not allocated\n", pasid);
> > > + else if (pdata == ERR_PTR(-EACCES))
> > > + pr_err("Free PASID %u by non-owner, denied", pasid);
> > > + else
> > > + pr_err("Error searching PASID %u\n", pasid);
> >
> > This should be removed, errno is sufficient for the user, this just
> > provides the user with a trivial DoS vector filling logs.
>
> sure, will fix it. thanks.
>
> > > + ret = -EPERM;
> >
> > But why not return PTR_ERR(pdata)?
>
> aha, would do it.
>
> > > + goto out_unlock;
> > > + }
> > > + if (pdata) {
> > > + pr_debug("Cannot free pasid %d with private data\n", pasid);
> > > + /* Expect PASID has no private data if not bond */
> > > + ret = -EBUSY;
> > > + goto out_unlock;
> > > + }
> > > + ioasid_free(pasid);
> >
> > We only ever get here with pasid == NULL?!
>
> I guess you meant only when pdata==NULL.
>
> > Something is wrong. Should
> > that be 'if (!pdata)'? (which also makes that pr_debug another DoS
> > vector)
>
> Oh, yes, just do it as below:
>
> if (!pdata) {
> ioasid_free(pasid);
> ret = SUCCESS;
> } else
> ret = -EBUSY;
>
> Is it what you mean?

No, I think I was just confusing pdata and pasid, but I am still
confused about testing pdata. We call ioasid_alloc() with private =
NULL, and I don't see any of your patches calling ioasid_set_data() to
change the private data after allocation, so how could this ever be
set? Should this just be a BUG_ON(pdata) as the integrity of the
system is in question should this state ever occur? Thanks,

Alex

> > > +
> > > +out_unlock:
> > > + if (mm)
> > > + mmput(mm);
> > > + mutex_unlock(&iommu->lock);
> > > + return ret;
> > > +}
> > > +
> > > static long vfio_iommu_type1_ioctl(void *iommu_data,
> > > unsigned int cmd, unsigned long arg)
> > > {
> > > @@ -2370,6 +2447,43 @@ static long vfio_iommu_type1_ioctl(void *iommu_data,
> > > &ustruct);
> > > mutex_unlock(&iommu->lock);
> > > return ret;
> > > +
> > > + } else if (cmd == VFIO_IOMMU_PASID_REQUEST) {
> > > + struct vfio_iommu_type1_pasid_request req;
> > > + int min_pasid, max_pasid, pasid;
> > > +
> > > + minsz = offsetofend(struct vfio_iommu_type1_pasid_request,
> > > + flag);
> > > +
> > > + if (copy_from_user(&req, (void __user *)arg, minsz))
> > > + return -EFAULT;
> > > +
> > > + if (req.argsz < minsz)
> > > + return -EINVAL;
> > > +
> > > + switch (req.flag) {
> >
> > This works, but it's strange. Let's make the code a little easier for
> > the next flag bit that gets used so they don't need to rework this case
> > statement. I'd suggest creating a VFIO_IOMMU_PASID_OPS_MASK that is
> > the OR of the ALLOC/FREE options, test that no bits are set outside of
> > that mask, then AND that mask as the switch arg with the code below.
>
> Got it. Let me fix it in next version.
>
> > > + /**
> > > + * TODO: min_pasid and max_pasid align with
> > > + * typedef unsigned int ioasid_t
> > > + */
> > > + case VFIO_IOMMU_PASID_ALLOC:
> > > + if (copy_from_user(&min_pasid,
> > > + (void __user *)arg + minsz, sizeof(min_pasid)))
> > > + return -EFAULT;
> > > + if (copy_from_user(&max_pasid,
> > > + (void __user *)arg + minsz + sizeof(min_pasid),
> > > + sizeof(max_pasid)))
> > > + return -EFAULT;
> > > + return vfio_iommu_type1_pasid_alloc(iommu,
> > > + min_pasid, max_pasid);
> > > + case VFIO_IOMMU_PASID_FREE:
> > > + if (copy_from_user(&pasid,
> > > + (void __user *)arg + minsz, sizeof(pasid)))
> > > + return -EFAULT;
> > > + return vfio_iommu_type1_pasid_free(iommu, pasid);
> > > + default:
> > > + return -EINVAL;
> > > + }
> > > }
> > >
> > > return -ENOTTY;
> > > diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
> > > index ccf60a2..04de290 100644
> > > --- a/include/uapi/linux/vfio.h
> > > +++ b/include/uapi/linux/vfio.h
> > > @@ -807,6 +807,31 @@ struct vfio_iommu_type1_cache_invalidate {
> > > };
> > > #define VFIO_IOMMU_CACHE_INVALIDATE _IO(VFIO_TYPE, VFIO_BASE + 24)
> > >
> > > +/*
> > > + * @flag=VFIO_IOMMU_PASID_ALLOC, refer to the @min_pasid and
> > @max_pasid fields
> > > + * @flag=VFIO_IOMMU_PASID_FREE, refer to @pasid field
> > > + */
> > > +struct vfio_iommu_type1_pasid_request {
> > > + __u32 argsz;
> > > +#define VFIO_IOMMU_PASID_ALLOC (1 << 0)
> > > +#define VFIO_IOMMU_PASID_FREE (1 << 1)
> > > + __u32 flag;
> > > + union {
> > > + struct {
> > > + int min_pasid;
> > > + int max_pasid;
> > > + };
> > > + int pasid;
> >
> > Perhaps:
> >
> > struct {
> > u32 min;
> > u32 max;
> > } alloc_pasid;
> > u32 free_pasid;
> >
> > (note also the s/int/u32/)
>
> got it. will fix it in next version. Thanks.
>
> > > + };
> > > +};
> > > +
> > > +/**
> > > + * VFIO_IOMMU_PASID_REQUEST - _IOWR(VFIO_TYPE, VFIO_BASE + 27,
> > > + * struct vfio_iommu_type1_pasid_request)
> > > + *
> > > + */
> > > +#define VFIO_IOMMU_PASID_REQUEST _IO(VFIO_TYPE, VFIO_BASE + 27)
> > > +
> > > /* -------- Additional API for SPAPR TCE (Server POWERPC) IOMMU -------- */
> > >
> > > /*
>
> Regards,
> Yi Liu