Re: [PATCH 2/4] dma-direct: leak memory that can't be re-encrypted

2021-10-21 Thread Christoph Hellwig
On Tue, Oct 19, 2021 at 12:56:36PM -0700, David Rientjes wrote: > > - dma_set_encrypted(dev, vaddr, 1 << page_order); > > + if (dma_set_encrypted(dev, vaddr, 1 << page_order)) { > > + pr_warn_ratelimited( > > + "leaking DMA memory that can't be re-encrypted\n"); > >

Re: [PATCH 2/4] dma-direct: leak memory that can't be re-encrypted

2021-10-19 Thread David Rientjes via iommu
On Tue, 19 Oct 2021, Christoph Hellwig wrote: > We must never unencryped memory go back into the general page pool. > So if we fail to set it back to encrypted when freeing DMA memory, leak > the memory insted and warn the user. > > Signed-off-by: Christoph Hellwig > --- > kernel/dma/direct.c

[PATCH 2/4] dma-direct: leak memory that can't be re-encrypted

2021-10-19 Thread Christoph Hellwig
We must never unencryped memory go back into the general page pool. So if we fail to set it back to encrypted when freeing DMA memory, leak the memory insted and warn the user. Signed-off-by: Christoph Hellwig --- kernel/dma/direct.c | 17 + 1 file changed, 13 insertions(+), 4