public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.pan@linux.microsoft.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-kernel@vger.kernel.org,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	Alex Williamson <alex@shazbot.org>,
	Joerg Roedel <joro@8bytes.org>,
	Mostafa Saleh <smostafa@google.com>,
	David Matlack <dmatlack@google.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Nicolin Chen <nicolinc@nvidia.com>,
	"Tian, Kevin" <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
	skhawaja@google.com, pasha.tatashin@soleen.com,
	Will Deacon <will@kernel.org>,
	Baolu Lu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH V3 03/10] iommufd: Allow binding to a noiommu device
Date: Fri, 10 Apr 2026 09:51:08 -0700	[thread overview]
Message-ID: <20260410095108.000006a0@linux.microsoft.com> (raw)
In-Reply-To: <20260409170657.GM3357077@nvidia.com>

Hi Jason,

On Thu, 9 Apr 2026 14:06:57 -0300
Jason Gunthorpe <jgg@nvidia.com> wrote:

> On Thu, Apr 02, 2026 at 10:11:39PM -0700, Jacob Pan wrote:
> > From: Jason Gunthorpe <jgg@nvidia.com>
> > 
> > Allow iommufd to bind devices without an IOMMU (noiommu mode) by
> > creating a dummy IOMMU group for such devices and skipping hwpt
> > operations.
> > 
> > This enables noiommu devices to operate through the same iommufd
> > API as IOMMU- capable devices.
> > 
> > Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> > Signed-off-by: Jacob Pan <jacob.pan@linux.microsoft.com>
> > 
> > ---
> > v3:
> >    - handle new error cases iommufd_device_bind. (Mostafa)
> > ---
> >  drivers/iommu/iommufd/device.c | 126
> > +++++++++++++++++++++++---------- 1 file changed, 87 insertions(+),
> > 39 deletions(-)  
> 
> 
> > @@ -294,11 +334,10 @@ struct iommufd_device
> > *iommufd_device_bind(struct iommufd_ctx *ictx, *id = idev->obj.id;
> >  	return idev;
> >  
> > -out_release_owner:
> > -	iommu_device_release_dma_owner(dev);
> > -out_group_put:
> > -	iommufd_put_group(igroup);
> > +err_out:
> > +	iommufd_object_abort_and_destroy(ictx, &idev->obj);
> >  	return ERR_PTR(rc);  
> 
> I fed this to Sashiko and it pointed out the abort flow here will call
> iommufd_device_destroy() bit it isn't prepared to handle a partially
> initialized idev. It looks like igroup is only set once it is
> sufficiently initialized so:
> 
> @@ -211,6 +211,8 @@ void iommufd_device_destroy(struct iommufd_object
> *obj) struct iommufd_device *idev =
>                 container_of(obj, struct iommufd_device, obj);
>  
> +       if (!idev->igroup)
> +               return;
>         if (!is_vfio_noiommu(idev))
>                 iommu_device_release_dma_owner(idev->dev);
>         iommufd_put_group(idev->igroup);
> 
> Should fix it, but lets add a comment because it is pretty fragile:
> 
> @@ -335,6 +337,10 @@ struct iommufd_device
> *iommufd_device_bind(struct iommufd_ctx *ictx, return idev;
>  
>  err_out:
> +       /*
> +        * Be careful that iommufd_device_destroy() can handle partial
> +        * initialization.
> +        */
>         iommufd_object_abort_and_destroy(ictx, &idev->obj);
>         return ERR_PTR(rc);
Yeah, will add to the next version.

Tested the error path by faking a failed group allocation, works as
expected.
#  RUN           vfio_noiommu.device_bind_iommufd ...
vfio_iommufd_noiommu_test.c:265:device_bind_iommufd:Expected 0 )
# device_bind_iommufd: Test terminated by assertion
#          FAIL  vfio_noiommu.device_bind_iommufd
not ok 17 vfio_noiommu.device_bind_iommufd



  reply	other threads:[~2026-04-10 16:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03  5:11 Jacob Pan
2026-04-03  5:11 ` [PATCH V3 01/10] iommufd: Support a HWPT without an iommu driver for noiommu Jacob Pan
2026-04-03  5:11 ` [PATCH V3 02/10] iommufd: Move igroup allocation to a function Jacob Pan
2026-04-03  5:11 ` [PATCH V3 03/10] iommufd: Allow binding to a noiommu device Jacob Pan
2026-04-09 17:06   ` Jason Gunthorpe
2026-04-10 16:51     ` Jacob Pan [this message]
2026-04-03  5:11 ` [PATCH V3 04/10] iommufd: Add an ioctl IOMMU_IOAS_GET_PA to query PA from IOVA Jacob Pan
2026-04-09 18:26   ` Jason Gunthorpe
2026-04-10 21:20     ` Jacob Pan
2026-04-03  5:11 ` [PATCH V3 05/10] vfio: Allow null group for noiommu without containers Jacob Pan
2026-04-09 18:44   ` Jason Gunthorpe
2026-04-10 23:09     ` Jacob Pan
2026-04-03  5:11 ` [PATCH V3 06/10] vfio: Introduce and set noiommu flag on vfio_device Jacob Pan
2026-04-03  5:11 ` [PATCH V3 07/10] vfio: Enable cdev noiommu mode under iommufd Jacob Pan
2026-04-09 18:48   ` Jason Gunthorpe
2026-04-03  5:11 ` [PATCH V3 08/10] vfio:selftest: Handle VFIO noiommu cdev Jacob Pan
2026-04-03  5:11 ` [PATCH V3 09/10] selftests/vfio: Add iommufd noiommu mode selftest for cdev Jacob Pan
2026-04-03  5:11 ` [PATCH V3 10/10] Documentation: Update VFIO NOIOMMU mode Jacob Pan

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=20260410095108.000006a0@linux.microsoft.com \
    --to=jacob.pan@linux.microsoft.com \
    --cc=alex@shazbot.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=dmatlack@google.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=robin.murphy@arm.com \
    --cc=skhawaja@google.com \
    --cc=smostafa@google.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox