projects / platform / kernel / linux-rpi.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 82b3f04) | patch
dma-direct: don't call dma_set_decrypted for remapped allocations
authorChristoph Hellwig <hch@lst.de>
Thu, 21 Oct 2021 07:20:39 +0000 (09:20 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 9 Jun 2022 08:23:03 +0000 (10:23 +0200)
commit9ba801c80c47c1283a570248d8ea3d139fb190d7
tree30b20d76da5a82777a04fef8f74ce35217ede818tree | snapshot
parent82b3f045aff5b6e40526d48f78b8fd9b0488aa34commit | diff
dma-direct: don't call dma_set_decrypted for remapped allocations

[ Upstream commit 5570449b6876f215d49ac4db9ccce6ff7aa1e20a ]

Remapped allocations handle the encrypted bit through the pgprot passed
to vmap, so there is no call dma_set_decrypted.  Note that this case is
currently entirely theoretical as no valid kernel configuration supports
remapped allocations and memory encryption currently.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>
kernel/dma/direct.c diff | blob | history
Domain: System / Kernel;