diff options
| author |   Mark Rutland <mark.rutland@arm.com> | 2022-04-27 18:31:25 +0100 |
|---|---|---|
| committer |   Kees Cook <keescook@chromium.org> | 2022-05-08 01:33:08 -0700 |
| commit | f03a50938decaa601f02294e4d057fb0048ca9ca (patch) | |
| tree | ab423d6a439df190bc88905c336210f424b5cc46 /scripts/generate_rust_analyzer.py | |
| parent | lkdtm/stackleak: rework boundary management (diff) | |
| download | wireguard-linux-f03a50938decaa601f02294e4d057fb0048ca9ca.tar.xz wireguard-linux-f03a50938decaa601f02294e4d057fb0048ca9ca.zip | |
lkdtm/stackleak: prevent unexpected stack usage
The lkdtm_STACKLEAK_ERASING() test is instrumentable and runs with IRQs
unmasked, so it's possible for unrelated code to clobber the task stack
and/or manipulate current->lowest_stack while the test is running,
resulting in spurious failures.
The regular stackleak erasing code is non-instrumentable and runs with
IRQs masked, preventing similar issues.
Make the body of the test non-instrumentable, and run it with IRQs
masked, avoiding such spurious failures.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Alexander Popov <alex.popov@linux.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Kees Cook <keescook@chromium.org>
Cc: Will Deacon <will@kernel.org>
Signed-off-by: Kees Cook <keescook@chromium.org>
Link: https://lore.kernel.org/r/20220427173128.2603085-11-mark.rutland@arm.com
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions