Linux IOMMU Development
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Vasant Hegde <vasant.hegde@amd.com>,
	iommu@lists.linux.dev, joro@8bytes.org
Cc: baolu.lu@linux.intel.com, robin.murphy@arm.com,
	suravee.suthikulpanit@amd.com
Subject: Re: [RFC PATCH] iommu: Handle domain allocation failure gracefully
Date: Thu, 15 Sep 2022 11:14:43 +0800	[thread overview]
Message-ID: <1a5195b4-eef2-00dd-1b16-806d662148ea@linux.intel.com> (raw)
In-Reply-To: <20220914144424.7356-1-vasant.hegde@amd.com>

On 9/14/22 10:44 PM, Vasant Hegde wrote:
> Current code does not validate domain allocation failures. This will
> result in random failure at later stage. Hence handle domain allocation
> failures.
> 
> Signed-off-by: Vasant Hegde<vasant.hegde@amd.com>
> ---
> Hi Joerg,
>    With current code whenever amd driver failes to allocate domain we hit
>    failure at late stage and it became difficult to debug. Hence I
>    thought of adding this fix.
> 
>    I see that in commit 6e1aa2049154 you have intentionally didn't check
>    the return value. Looking into drivers/iommu/* it looks like all
>    drivers has domain_alloc() callback handler. But some drivers (like msm
>    - msm_iommu_domain_alloc()) allocates default domain for certain type
>    only. Hence I'm not sure whether its ok to handle domain allocation
>    failures or not. Hence I have marked this patch as RFC.
> 
>    Let me know whether this patch is fine -OR- is there any other way we can
>    handle domain allocation failures?
> 
> -Vasant
> 
>   drivers/iommu/iommu.c | 24 +++++++++++++-----------
>   1 file changed, 13 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index 780fb7071577..e8a1e7fbffb9 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -289,18 +289,21 @@ int iommu_probe_device(struct device *dev)
>   
>   	/*
>   	 * Try to allocate a default domain - needs support from the
> -	 * IOMMU driver. There are still some drivers which don't
> -	 * support default domains, so the return value is not yet
> -	 * checked.
> +	 * IOMMU driver.
>   	 */
>   	mutex_lock(&group->mutex);
> -	iommu_alloc_default_domain(group, dev);
> +	ret = iommu_alloc_default_domain(group, dev);
> +	if (ret) {
> +		mutex_unlock(&group->mutex);
> +		iommu_group_put(group);
> +		goto err_release;
> +	}

Some IOMMU drivers (s390, gart, tegra...) don't support default domains.
iommu_alloc_default_domain() returns a ENOMEM and the probe process
continues.

Above changes this behavior. The probe process will always fails with
those IOMMU drivers.

Best regards,
baolu

  reply	other threads:[~2022-09-15  3:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 14:44 [RFC PATCH] iommu: Handle domain allocation failure gracefully Vasant Hegde
2022-09-15  3:14 ` Baolu Lu [this message]
2022-09-15  6:13   ` Vasant Hegde
2022-09-15  7:28     ` Baolu Lu
2022-10-20 14:49       ` Vasant Hegde

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=1a5195b4-eef2-00dd-1b16-806d662148ea@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=robin.murphy@arm.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.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