summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorJeremy Linton <jeremy.linton@arm.com>2020-05-04 23:13:48 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-05-05 14:06:46 +0300
commit2bef9aed6f0e22391c8d4570749b1acc9bc3981e (patch)
tree89f8f8a511a9cdb4b3d8e0e148106f7128032a23 /tools/perf/scripts/python/stackcollapse.py
parente283f5e89f44a80ca536e4a12903c64e9e9a82e4 (diff)
downloadlinux-2bef9aed6f0e22391c8d4570749b1acc9bc3981e.tar.xz
usb: usbfs: correct kernel->user page attribute mismatch
On some architectures (e.g. arm64) requests for IO coherent memory may use non-cachable attributes if the relevant device isn't cache coherent. If these pages are then remapped into userspace as cacheable, they may not be coherent with the non-cacheable mappings. In particular this happens with libusb, when it attempts to create zero-copy buffers for use by rtl-sdr (https://github.com/osmocom/rtl-sdr/). On low end arm devices with non-coherent USB ports, the application will be unexpectedly killed, while continuing to work fine on arm machines with coherent USB controllers. This bug has been discovered/reported a few times over the last few years. In the case of rtl-sdr a compile time option to enable/disable zero copy was implemented to work around it. Rather than relaying on application specific workarounds, dma_mmap_coherent() can be used instead of remap_pfn_range(). The page cache/etc attributes will then be correctly set in userspace to match the kernel mapping. Signed-off-by: Jeremy Linton <jeremy.linton@arm.com> Cc: stable <stable@vger.kernel.org> Link: https://lore.kernel.org/r/20200504201348.1183246-1-jeremy.linton@arm.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions