diff options
| author |   Alexander Gordeev <agordeev@linux.ibm.com> | 2025-08-18 18:39:13 +0200 |
|---|---|---|
| committer |   Andrew Morton <akpm@linux-foundation.org> | 2025-08-27 22:45:42 -0700 |
| commit | c519c3c0a1133c408e83a383aa4dd30010aa5d71 (patch) | |
| tree | 4ce13380bea40296ee195d2b18c35e4d9b6eff92 /rust/pin-init/internal/src | |
| parent | mm/kasan: fix vmalloc shadow memory (de-)population races (diff) | |
| download | wireguard-linux-c519c3c0a1133c408e83a383aa4dd30010aa5d71.tar.xz wireguard-linux-c519c3c0a1133c408e83a383aa4dd30010aa5d71.zip | |
mm/kasan: avoid lazy MMU mode hazards
Functions __kasan_populate_vmalloc() and __kasan_depopulate_vmalloc() use
apply_to_pte_range(), which enters lazy MMU mode. In that mode updating
PTEs may not be observed until the mode is left.
That may lead to a situation in which otherwise correct reads and writes
to a PTE using ptep_get(), set_pte(), pte_clear() and other access
primitives bring wrong results when the vmalloc shadow memory is being
(de-)populated.
To avoid these hazards leave the lazy MMU mode before and re-enter it
after each PTE manipulation.
Link: https://lkml.kernel.org/r/0d2efb7ddddbff6b288fbffeeb10166e90771718.1755528662.git.agordeev@linux.ibm.com
Fixes: 3c5c3cfb9ef4 ("kasan: support backing vmalloc space with real shadow memory")
Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Daniel Axtens <dja@axtens.net>
Cc: Marc Rutland <mark.rutland@arm.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'rust/pin-init/internal/src')
0 files changed, 0 insertions, 0 deletions