Re: [PATCH] dma-direct: Don't over-decrypt memory

On Fri, 20 May 2022, Robin Murphy wrote: > The original x86 sev_alloc() only called set_memory_decrypted() on > memory returned by alloc_pages_node(), so the page order calculation > fell out of that logic. However, the common dma-direct code has several > potential allocators, not all of which

Re: [PATCH] dma-direct: Don't over-decrypt memory

Thanks, applied to the dma-mapping for-next branch. ___ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu

[PATCH] dma-direct: Don't over-decrypt memory

The original x86 sev_alloc() only called set_memory_decrypted() on memory returned by alloc_pages_node(), so the page order calculation fell out of that logic. However, the common dma-direct code has several potential allocators, not all of which are guaranteed to round up the underlying