linux-kernel - SWIOTLB on 32-bit PAE

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>] [day] [month] [year] [list]

Message-ID: <5612356B.7070301@t2data.com>
Date:	Mon, 5 Oct 2015 10:31:39 +0200
From:	Christian Melki <christian.melki@...ata.com>
To:	<linux-kernel@...r.kernel.org>
CC:	<konrad.wilk@...cle.com>
Subject: SWIOTLB on 32-bit PAE

Hi,

I discovered that my 32-bit PAE 4.2.0 kernel (no IOMMU code) would hang 
when writing to my USB disk. The kernel spews million(-ish messages per 
sec) to syslog, effectively "hanging" userspace with my kernel.

Oct  2 14:33:06 voodoochild kernel: [  223.287447] nommu_map_sg: 
overflow 25dcac000+1024 of device mask ffffffff
Oct  2 14:33:06 voodoochild kernel: [  223.287448] nommu_map_sg: 
overflow 25dcac000+1024 of device mask ffffffff
Oct  2 14:33:06 voodoochild kernel: [  223.287449] nommu_map_sg: 
overflow 25dcac000+1024 of device mask ffffffff
... etc ...

In my kernel config I noticed that SWIOTLB was not on. It seems SWIOTLB 
is provided for 64-bit and 32-bit with IOMMU/AGPGART code. But if I 
compiled the kernel with PAE and no IOMMU and no other GART code, I 
would not get SWIOTLB. I'd like to think that SWIOTLB should be selected 
for 32-bit PAE as default.

I have attached a oneliner patch which does that.
The patch works for me. The issue where the kernel more or less runs 
endless bashing of (nommu_?)map_sg when failing is another problem I 
guess. I expected the kernel/drivers to have some more graceful 
handling, but I know to little about this area to have a proper opinion.

Regards,
Christian

View attachment "swiotlb.patch" of type "text/x-patch" (482 bytes)