linux-kernel - Re: AMD IOMMU causing filesystem corruption

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 26 Apr 2017 14:31:40 -0700
From:   Samuel Sieb <samuel@...b.net>
To:     Joerg Roedel <joro@...tes.org>
Cc:     Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: AMD IOMMU causing filesystem corruption

On 04/26/2017 03:14 AM, Joerg Roedel wrote:
> On Tue, Apr 25, 2017 at 10:55:24AM -0700, Samuel Sieb wrote:
>> On 04/07/2017 03:27 AM, Joerg Roedel wrote:
>>> Also, please try the attached debug-diff on your kernel. It completly
>>> disables the use of ATS in the amd-iommu driver.
>>>
>> I applied this patch to 4.11.0 rc8 and then stress tested the laptop
>> with another kernel build while running graphical applications and
>> there appears to be no damage to the filesystem.  Is there any way
>> to determine if ATS is enabled or disabled?
> 
> Great, thanks for testing the patch. The lspci tool should be able to
> tell you whether the ATS capability is enabled on the GPU. With a
> 'lspci -vvv -s <GPUDEV>" should give you that info.
> 
This test was done with the patch that always disables ATS.  Which is 
the current patch to selectively disable it?  The last patch I tried 
didn't seem to work.