summaryrefslogtreecommitdiffstats
path: root/crypto/gcm.c
diff options
context:
space:
mode:
authorJoerg Roedel <jroedel@suse.de>2019-09-06 10:39:54 +0200
committerJoerg Roedel <jroedel@suse.de>2019-09-06 10:55:51 +0200
commit754265bcab78a9014f0f99cd35e0d610fcd7dfa7 (patch)
tree0e0ea57c5cc3aa674e93746a1d96b4ce4b8d9987 /crypto/gcm.c
parentiommu/amd: Flush old domains in kdump kernel (diff)
downloadlinux-754265bcab78a9014f0f99cd35e0d610fcd7dfa7.tar.xz
linux-754265bcab78a9014f0f99cd35e0d610fcd7dfa7.zip
iommu/amd: Fix race in increase_address_space()
After the conversion to lock-less dma-api call the increase_address_space() function can be called without any locking. Multiple CPUs could potentially race for increasing the address space, leading to invalid domain->mode settings and invalid page-tables. This has been happening in the wild under high IO load and memory pressure. Fix the race by locking this operation. The function is called infrequently so that this does not introduce a performance regression in the dma-api path again. Reported-by: Qian Cai <cai@lca.pw> Fixes: 256e4621c21a ('iommu/amd: Make use of the generic IOVA allocator') Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'crypto/gcm.c')
0 files changed, 0 insertions, 0 deletions