summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorSasha Levin <sashal@kernel.org>2022-05-18 22:28:18 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-05-25 10:17:55 +0300
commite2cfa7b0935c2445cd7a2919f91831a0f9821c3d (patch)
tree586591cc91cbadf7b1523d72dc3589c7247d1f08 /include/linux
parentfe5ac3da50a92764bd534a39f851c744f0d4e2c3 (diff)
downloadlinux-e2cfa7b0935c2445cd7a2919f91831a0f9821c3d.tar.xz
Revert "swiotlb: fix info leak with DMA_FROM_DEVICE"
This reverts commit d4d975e7921079f877f828099bb8260af335508f. Upstream had a follow-up fix, revert, and a semi-reverted-revert. Instead of going through this chain which is more painful to backport, I'm just going to revert this original commit and pick the final one. Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include/linux')
-rw-r--r--include/linux/dma-mapping.h8
1 files changed, 0 insertions, 8 deletions
diff --git a/include/linux/dma-mapping.h b/include/linux/dma-mapping.h
index a9361178c5db..a7d70cdee25e 100644
--- a/include/linux/dma-mapping.h
+++ b/include/linux/dma-mapping.h
@@ -62,14 +62,6 @@
#define DMA_ATTR_PRIVILEGED (1UL << 9)
/*
- * This is a hint to the DMA-mapping subsystem that the device is expected
- * to overwrite the entire mapped size, thus the caller does not require any
- * of the previous buffer contents to be preserved. This allows
- * bounce-buffering implementations to optimise DMA_FROM_DEVICE transfers.
- */
-#define DMA_ATTR_OVERWRITE (1UL << 10)
-
-/*
* A dma_addr_t can hold any valid DMA or bus address for the platform. It can
* be given to a device to use as a DMA source or target. It is specific to a
* given device and there may be a translation between the CPU physical address