aboutsummaryrefslogtreecommitdiffstats
path: root/security/selinux/hooks.c
diff options
context:
space:
mode:
authorMichael S. Tsirkin <[email protected]>2017-02-03 03:43:52 +0000
committerMichael S. Tsirkin <[email protected]>2017-02-03 21:38:50 +0000
commit0d5415b489f68b58e1983a53793d25d53098ed4b (patch)
tree9509a05b5c480b84214714698cffb85943be8124 /security/selinux/hooks.c
parentLinux 4.10-rc6 (diff)
downloadkernel-0d5415b489f68b58e1983a53793d25d53098ed4b.tar.gz
kernel-0d5415b489f68b58e1983a53793d25d53098ed4b.zip
Revert "vring: Force use of DMA API for ARM-based systems with legacy devices"
This reverts commit c7070619f3408d9a0dffbed9149e6f00479cf43b. This has been shown to regress on some ARM systems: by forcing on DMA API usage for ARM systems, we have inadvertently kicked open a hornets' nest in terms of cache-coherency. Namely that unless the virtio device is explicitly described as capable of coherent DMA by firmware, the DMA APIs on ARM and other DT-based platforms will assume it is non-coherent. This turns out to cause a big problem for the likes of QEMU and kvmtool, which generate virtio-mmio devices in their guest DTs but neglect to add the often-overlooked "dma-coherent" property; as a result, we end up with the guest making non-cacheable accesses to the vring, the host doing so cacheably, both talking past each other and things going horribly wrong. We are working on a safer work-around. Fixes: c7070619f340 ("vring: Force use of DMA API for ARM-based systems with legacy devices") Reported-by: Robin Murphy <[email protected]> Cc: <[email protected]> Signed-off-by: Will Deacon <[email protected]> Signed-off-by: Michael S. Tsirkin <[email protected]> Acked-by: Marc Zyngier <[email protected]>
Diffstat (limited to 'security/selinux/hooks.c')
0 files changed, 0 insertions, 0 deletions