From: Robin Murphy <robin.murphy@arm.com>
To: Kunkun Jiang <jiangkunkun@huawei.com>,
Will Deacon <will@kernel.org>, Eric Auger <eric.auger@redhat.com>,
"moderated list:ARM SMMU DRIVERS"
<linux-arm-kernel@lists.infradead.org>,
"open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
open list <linux-kernel@vger.kernel.org>
Cc: wanghaibin.wang@huawei.com
Subject: Re: [RFC PATCH v1 0/2] iommu/arm-smmu-v3: Add some parameter check in __arm_smmu_tlb_inv_range()
Date: Wed, 19 May 2021 11:01:33 +0100 [thread overview]
Message-ID: <c577a7cc-8db3-5802-53cb-985f0c7216b3@arm.com> (raw)
In-Reply-To: <20210519094307.3275-1-jiangkunkun@huawei.com>
On 2021-05-19 10:43, Kunkun Jiang wrote:
> Hi all,
>
> This set of patches solves some errors when I tested the SMMU nested mode.
>
> Test scenario description:
> guest kernel: 4KB translation granule
> host kernel: 16KB translation granule
>
> errors:
> 1. encountered an endless loop in __arm_smmu_tlb_inv_range because
> num_pages is 0
> 2. encountered CERROR_ILL because the fields of TLB invalidation
> command are as follow: TG = 2, NUM = 0, SCALE = 0, TTL = 0. The
> combination is exactly the kind of reserved combination pointed
> out in the SMMUv3 spec(page 143-144, version D.a)
>
> In my opinion, it is more appropriate to add parameter check in
> __arm_smmu_tlb_inv_range(), although these problems only appeared
> when I tested the SMMU nested mode. What do you think?
FWIW I think it would be better to fix the caller to not issue broken
commands in the first place. The kernel shouldn't do so for itself (and
definitely needs fixing if it ever does), so it sounds like the nesting
implementation needs to do a bit more validation of what it's passing
through.
Robin.
> This series include patches as below:
> Patch 1:
> - align the invalid range with leaf page size upwards when smmu
> supports RIL
>
> Patch 2:
> - add a check to standardize granule size when smmu supports RIL
>
> Kunkun Jiang (2):
> iommu/arm-smmu-v3: Align invalid range with leaf page size upwards
> when support RIL
> iommu/arm-smmu-v3: Standardize granule size when support RIL
>
> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-19 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 9:43 [RFC PATCH v1 0/2] iommu/arm-smmu-v3: Add some parameter check in __arm_smmu_tlb_inv_range() Kunkun Jiang
2021-05-19 9:43 ` [RFC PATCH v1 1/2] iommu/arm-smmu-v3: Align invalid range with leaf page size upwards when support RIL Kunkun Jiang
2021-05-19 9:43 ` [RFC PATCH v1 2/2] iommu/arm-smmu-v3: Standardize granule size " Kunkun Jiang
2021-05-19 10:01 ` Robin Murphy [this message]
2021-05-21 6:53 ` [RFC PATCH v1 0/2] iommu/arm-smmu-v3: Add some parameter check in __arm_smmu_tlb_inv_range() Kunkun Jiang
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=c577a7cc-8db3-5802-53cb-985f0c7216b3@arm.com \
--to=robin.murphy@arm.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jiangkunkun@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wanghaibin.wang@huawei.com \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).