| Message ID | 1404905415-9046-6-git-send-email-a.ryabinin@samsung.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Andrey Ryabinin <a.ryabinin@samsung.com> writes:
> Instrumentation of this files may result in unbootable machine.
This doesn't make sense. Is the code not NMI safe?
If yes that would need to be fixed because
Please debug more.
perf is a common source of bugs (see Vice Weaver's fuzzer results),
so it would be good to have this functionality for it.
-Andi
On 07/09/14 23:33, Andi Kleen wrote: > Andrey Ryabinin <a.ryabinin@samsung.com> writes: > >> Instrumentation of this files may result in unbootable machine. > > This doesn't make sense. Is the code not NMI safe? > If yes that would need to be fixed because > > Please debug more. > Sure. It turns out that KASAN_SANITIZE_perf_event.o := n is not needed here. The problem only with common.c > perf is a common source of bugs (see Vice Weaver's fuzzer results), > so it would be good to have this functionality for it. > > -Andi >
diff --git a/arch/x86/kernel/cpu/Makefile b/arch/x86/kernel/cpu/Makefile index 7fd54f0..a7bb360 100644 --- a/arch/x86/kernel/cpu/Makefile +++ b/arch/x86/kernel/cpu/Makefile @@ -8,6 +8,9 @@ CFLAGS_REMOVE_common.o = -pg CFLAGS_REMOVE_perf_event.o = -pg endif +KASAN_SANITIZE_common.o := n +KASAN_SANITIZE_perf_event.o := n + # Make sure load_percpu_segment has no stackprotector nostackp := $(call cc-option, -fno-stack-protector) CFLAGS_common.o := $(nostackp)
Instrumentation of this files may result in unbootable machine. Signed-off-by: Andrey Ryabinin <a.ryabinin@samsung.com> --- arch/x86/kernel/cpu/Makefile | 3 +++ 1 file changed, 3 insertions(+)