[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19d57dfd-12df-9237-3576-32b0feef90fa@arm.com>
Date: Tue, 18 Feb 2020 18:31:51 +0000
From: Robin Murphy <robin.murphy@....com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Sasha Levin <sashal@...nel.org>, iommu@...ts.linux-foundation.org,
robdclark@...il.com, bjorn.andersson@...aro.org,
Nicolas Dechesne <nicolas.dechesne@...aro.org>,
Will Deacon <will@...nel.org>, joro@...tes.org,
masneyb@...tation.org, lkft-triage@...ts.linaro.org,
open list <linux-kernel@...r.kernel.org>,
linux- stable <stable@...r.kernel.org>,
linux-arm-msm@...r.kernel.org
Subject: Re: drivers/iommu/qcom_iommu.c:348 qcom_iommu_domain_free+0x5c/0x70
On 18/02/2020 6:23 pm, Greg Kroah-Hartman wrote:
[...]
> Can you bisect to find the offending commit?
This particular presentation appears to be down to the DRM driver
starting to call of_platform_depopulate(), but it's merely exposing
badness in the IOMMU driver that's been there from day 1. I just sent a
fix for that[1].
Robin.
[1]
https://lore.kernel.org/linux-iommu/be92829c6e5467634b109add002351e6cf9e18d2.1582049382.git.robin.murphy@arm.com/
Powered by blists - more mailing lists