diff options
author | Will Deacon <will@kernel.org> | 2019-12-19 17:22:31 +0300 |
---|---|---|
committer | Will Deacon <will@kernel.org> | 2020-04-16 14:28:34 +0300 |
commit | dee081bf8f824cabeb7c7495367d5dad0a444eb1 (patch) | |
tree | eb19a451dd6f475428f2775d4d06c491b4ee4b01 /tools/perf/scripts/python/mem-phys-addr.py | |
parent | 9e343b467c70379e66b8b771d96f03ae23eba351 (diff) | |
download | linux-dee081bf8f824cabeb7c7495367d5dad0a444eb1.tar.xz |
READ_ONCE: Drop pointer qualifiers when reading from scalar types
Passing a volatile-qualified pointer to READ_ONCE() is an absolute
trainwreck for code generation: the use of 'typeof()' to define a
temporary variable inside the macro means that the final evaluation in
macro scope ends up forcing a read back from the stack. When stack
protector is enabled (the default for arm64, at least), this causes
the compiler to vomit up all sorts of junk.
Unfortunately, dropping pointer qualifiers inside the macro poses quite
a challenge, especially since the pointed-to type is permitted to be an
aggregate, and this is relied upon by mm/ code accessing things like
'pmd_t'. Based on numerous hacks and discussions on the mailing list,
this is the best I've managed to come up with.
Introduce '__unqual_scalar_typeof()' which takes an expression and, if
the expression is an optionally qualified 8, 16, 32 or 64-bit scalar
type, evaluates to the unqualified type. Other input types, including
aggregates, remain unchanged. Hopefully READ_ONCE() on volatile aggregate
pointers isn't something we do on a fast-path.
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Reported-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions