diff options
| author | Arnd Bergmann <[email protected]> | 2023-08-17 00:23:34 +0100 |
|---|---|---|
| committer | Palmer Dabbelt <[email protected]> | 2023-09-01 09:07:44 -0700 |
| commit | eb746180132a555da8cfb02d98cb6d0a9d58e870 (patch) | |
| tree | 7a13de90b7e8c4403b3ca2ca9b92112b5de03246 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5 (diff) | |
riscv: dma-mapping: only invalidate after DMA, not flush
No other architecture intentionally writes back dirty cache lines into
a buffer that a device has just finished writing into. If the cache is
clean, this has no effect at all, but if a cacheline in the buffer has
actually been written by the CPU, there is a driver bug that is likely
made worse by overwriting that buffer.
Signed-off-by: Arnd Bergmann <[email protected]>
Reviewed-by: Conor Dooley <[email protected]>
Reviewed-by: Lad Prabhakar <[email protected]>
Acked-by: Palmer Dabbelt <[email protected]>
Signed-off-by: Lad Prabhakar <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Palmer Dabbelt <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions