[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131014124837.GD10491@mudshark.cambridge.arm.com>
Date: Mon, 14 Oct 2013 13:48:37 +0100
From: Will Deacon <will.deacon@....com>
To: Antonios Motakis <a.motakis@...tualopensystems.com>
Cc: Joerg Roedel <joro@...tes.org>,
"moderated list:ARM SMMU DRIVER"
<linux-arm-kernel@...ts.infradead.org>,
"open list:IOMMU DRIVERS" <iommu@...ts.linux-foundation.org>,
open list <linux-kernel@...r.kernel.org>,
"kvmarm@...ts.cs.columbia.edu" <kvmarm@...ts.cs.columbia.edu>,
"tech@...tualopensystems.com" <tech@...tualopensystems.com>,
"agraf@...e.de" <agraf@...e.de>,
"B08248@...escale.com" <B08248@...escale.com>
Subject: Re: [PATCH 2/2] ARM: SMMU: return NULL on error in
arm_smmu_iova_to_phys
On Fri, Oct 11, 2013 at 02:24:47PM +0100, Antonios Motakis wrote:
> The return value of arm_smmu_iova_to_phys is directly passed to the
> user of the IOMMU API via iommu_iova_to_phys; however the ARM SMMU
> driver returns -EINVAL on error, which is not consistent with the
> rest of the drivers implementing the IOMMU API. VFIO also relies on
> the call returning NULL when a page has not been mapped already.
>
> Signed-off-by: Antonios Motakis <a.motakis@...tualopensystems.com>
> ---
> drivers/iommu/arm-smmu.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/iommu/arm-smmu.c b/drivers/iommu/arm-smmu.c
> index 8b71332..fe81b20 100644
> --- a/drivers/iommu/arm-smmu.c
> +++ b/drivers/iommu/arm-smmu.c
> @@ -1480,10 +1480,7 @@ static phys_addr_t arm_smmu_iova_to_phys(struct iommu_domain *domain,
>
> err_unlock:
> spin_unlock(&smmu_domain->lock);
> - dev_warn(smmu->dev,
> - "invalid (corrupt?) page tables detected for iova 0x%llx\n",
> - (unsigned long long)iova);
> - return -EINVAL;
> + return NULL;
Why are you removing the warning message?
Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists