[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5e119919-bbfd-14a4-0258-93e8249d11c4@nvidia.com>
Date: Tue, 4 Jun 2019 12:35:05 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Christoph Hellwig <hch@....de>
CC: Robin Murphy <robin.murphy@....com>,
Joerg Roedel <joro@...tes.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Tom Lendacky <thomas.lendacky@....com>,
<iommu@...ts.linux-foundation.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>,
linux-tegra <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH 07/26] iommu/dma: move the arm64 wrappers to common code
On 04/06/2019 07:05, Christoph Hellwig wrote:
> On Mon, Jun 03, 2019 at 08:47:57PM +0100, Jon Hunter wrote:
>> Since next-20190529 one of our tests for MMC has started failing, where
>> the symptom is that the data written to the MMC does not match the
>> source. Bisecting this is pointing to this commit. Unfortunately, I am
>> not able to cleanly revert this on top of -next, but wanted to report
>> this if case you have any ideas.
>
> Does this fix your problem?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git/commit/?h=generic-dma-ops&id=1b961423158caaae49d3900b7c9c37477bbfa9b3
Yes I can confirm with this patch on today's -next the issue is no
longer seen, and reverting this patch on top of today's -next causes the
problem to occur again. So yes this fixes my problem.
Thanks!
Jon
--
nvpublic
Powered by blists - more mailing lists