On Wed, 9 Jul 2025 at 21:56, Jason Gunthorpe jgg@nvidia.com wrote:
On Wed, Jul 09, 2025 at 04:14:26PM +0530, Naresh Kamboju wrote:
I have tested this patch on top of Linux next-20250702 tag, and found kernel warning,
Oh, yeah, I guess that hacky fix is not going to work.
Then this is probably good enough (against linux-next):
--- a/drivers/iommu/arm/arm-smmu/qcom_iommu.c +++ b/drivers/iommu/arm/arm-smmu/qcom_iommu.c @@ -335,7 +335,7 @@ static struct iommu_domain *qcom_iommu_domain_alloc_paging(struct device *dev)
mutex_init(&qcom_domain->init_mutex); spin_lock_init(&qcom_domain->pgtbl_lock);
qcom_domain->domain.pgsize_bitmap = SZ_4K | SZ_64K | SZ_1M | SZ_16M;
qcom_domain->domain.pgsize_bitmap = SZ_4K | SZ_2M; return &qcom_domain->domain;
}
I have tested the above patch and it fixes the reported issue.
Tested-by: Linux Kernel Functional Testing lkft@linaro.org
* https://lkft.validation.linaro.org/scheduler/job/8351756#L2565
-- Linaro LKFT https://lkft.linaro.org