Re: [PATCH v2] dma-direct: set decrypted flag for remapped DMA allocations

[Jason Gunthorpe]

On Fri, Jan 02, 2026 at 09:20:37PM +0530, Aneesh Kumar K.V (Arm) wrote:
> Devices that are DMA non-coherent and require a remap were skipping
> dma_set_decrypted(), leaving DMA buffers encrypted even when the device
> requires unencrypted access. Move the call after the if (remap) branch
> so that both the direct and remapped allocation paths correctly mark the
> allocation as decrypted (or fail cleanly) before use.

This is probably fine, but IMHO, we should be excluding the
combination of highmem and CC at the kconfig level :\

Jason