diff options
| author | Peter Zijlstra <peterz@infradead.org> | 2022-07-08 09:18:06 +0200 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2022-07-21 10:50:13 -0700 |
| commit | b67fbebd4cf980aecbcc750e1462128bffe8ae15 (patch) | |
| tree | 96e359e543dd17dae340b5d87903027228c3ca92 /MAINTAINERS | |
| parent | 18ba064e42df3661e196ab58a23931fc732a420b (diff) | |
| download | linux-b67fbebd4cf980aecbcc750e1462128bffe8ae15.tar.bz2 | |
mmu_gather: Force tlb-flush VM_PFNMAP vmas
Jann reported a race between munmap() and unmap_mapping_range(), where
unmap_mapping_range() will no-op once unmap_vmas() has unlinked the
VMA; however munmap() will not yet have invalidated the TLBs.
Therefore unmap_mapping_range() will complete while there are still
(stale) TLB entries for the specified range.
Mitigate this by force flushing TLBs for VM_PFNMAP ranges.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Will Deacon <will@kernel.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions