Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Linus Torvalds b2f140a9f9 Reinstate some of "swiotlb: rework "fix info leak with DMA_FROM_DEVICE"" ... commit 901c7280ca0d5e2b4a8929fbe0bfb007ac2a6544 upstream. Halil Pasic points out [1] that the full revert of that commit (revert in bddac7c1e02b), and that a partial revert that only reverts the problematic case, but still keeps some of the cleanups is probably better.  And that partial revert [2] had already been verified by Oleksandr Natalenko to also fix the issue, I had just missed that in the long discussion. So let's reinstate the cleanups from commit aa6f8dcbab47 ("swiotlb: rework "fix info leak with DMA_FROM_DEVICE""), and effectively only revert the part that caused problems. Link: https://lore.kernel.org/all/20220328013731.017ae3e3.pasic@linux.ibm.com/ [1] Link: https://lore.kernel.org/all/20220324055732.GB12078@lst.de/ [2] Link: https://lore.kernel.org/all/4386660.LvFx2qVVIh@natalenko.name/ [3] Suggested-by: Halil Pasic <pasic@linux.ibm.com> Tested-by: Oleksandr Natalenko <oleksandr@natalenko.name> Cc: Christoph Hellwig" <hch@lst.de> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> [OP: backport to 5.4: adjusted context] Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2022-05-25 09:14:38 +02:00
..
coherent.c	dma-coherent: fix integer overflow in the reserved-memory dma allocation	2020-04-23 10:36:30 +02:00
contiguous.c
debug.c	dma-debug: fix return value of __setup handlers	2022-04-15 14:18:18 +02:00
direct.c	dma-direct: avoid redundant memory sync for swiotlb	2022-04-20 09:19:39 +02:00
dummy.c
Kconfig
Makefile
mapping.c
remap.c
swiotlb.c	Reinstate some of "swiotlb: rework "fix info leak with DMA_FROM_DEVICE""	2022-05-25 09:14:38 +02:00
virt.c