Re: [PATCH] iommufd: Do not allow _iommufd_object_alloc_ucmd if abort op is set

[Jason Gunthorpe <jgg@nvidia.com>]

On Thu, Jul 10, 2025 at 01:23:54PM -0700, Nicolin Chen wrote:
> An abort op was introduced to allow its caller to invoke it within a lock
> in the caller's function. On the other hand, _iommufd_object_alloc_ucmd()
> would invoke the abort op in iommufd_object_abort_and_destroy() that must
> be outside the caller's lock. So, these two cannot work together.
> 
> Add a validation in the _iommufd_object_alloc_ucmd(). Pick -EOPNOTSUPP to
> reject the function call, indicating that the object allocator is buggy.
> 
> Suggested-by: Xu Yilun <yilun.xu@linux.intel.com>
> Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>
> ---
>  drivers/iommu/iommufd/main.c | 9 +++++++++
>  1 file changed, 9 insertions(+)

Applied

Thanks,
Jason