diff options
author | Vasily Gorbik <gor@linux.ibm.com> | 2019-08-13 19:23:51 +0200 |
---|---|---|
committer | Vasily Gorbik <gor@linux.ibm.com> | 2019-08-21 12:58:53 +0200 |
commit | 2c7fa8a11cc528e49e88352fce8cf083104b3797 (patch) | |
tree | 5bdb4f2c07e83410c0cdd0b299aed23e489fb3b3 /arch/s390/Kconfig | |
parent | s390/process: avoid potential reading of freed stack (diff) | |
download | linux-dev-2c7fa8a11cc528e49e88352fce8cf083104b3797.tar.xz linux-dev-2c7fa8a11cc528e49e88352fce8cf083104b3797.zip |
s390/kasan: avoid report in get_wchan
Reading other running task's stack can be a dangerous endeavor. Kasan
stack memory access instrumentation includes special prologue and epilogue
to mark/remove red zones in shadow memory between stack variables. For
that reason there is always a race between a task reading value in other
task's stack and that other task returning from a function and entering
another one generating different red zones pattern.
To avoid kasan reports simply perform uninstrumented memory reads.
Acked-by: Ilya Leoshkevich <iii@linux.ibm.com>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Diffstat (limited to 'arch/s390/Kconfig')
0 files changed, 0 insertions, 0 deletions