compiler: introduce __no_sanitize_address_or_inline
authorVasily Gorbik <gor@linux.ibm.com>
Mon, 20 Nov 2017 10:16:14 +0000 (11:16 +0100)
committerMartin Schwidefsky <schwidefsky@de.ibm.com>
Tue, 9 Oct 2018 09:21:25 +0000 (11:21 +0200)
commitdde709d1361ab50d3b9f2824f72b4374f5582e84
tree441e7bde41fc063c7f23f31578560ca6174d6f16
parentd58106c3ec9abcf2f9882171d6230eccfd6dc52e
compiler: introduce __no_sanitize_address_or_inline

Due to conflict between kasan instrumentation and inlining
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67368 functions which are
defined as inline could not be called from functions defined with
__no_sanitize_address.

Introduce __no_sanitize_address_or_inline which would expand to
__no_sanitize_address when the kernel is built with kasan support and
to inline otherwise. This helps to avoid disabling kasan
instrumentation for entire files.

Reviewed-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
include/linux/compiler-gcc.h