[tip:kmemcheck] kmemcheck: make ftrace and kmemcheck mutually exclusive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Author:     Vegard Nossum <vegard.nossum@xxxxxxxxx>
AuthorDate: Sun, 22 Feb 2009 18:40:24 +0100
Commit:     Vegard Nossum <vegard.nossum@xxxxxxxxx>
CommitDate: Sun, 22 Feb 2009 18:40:24 +0100

kmemcheck: make ftrace and kmemcheck mutually exclusive

The function tracer will be called on page-fault entry, and it
will access its internal structures, resulting in a recursive
page fault.

There are generally three ways to fix this:

1. Don't trace page faults if kmemcheck is compiled in.
2. Don't access tracked memory in ftrace.
3. Disallow kmemcheck and ftrace to be compiled in at the same
   time.

We choose the easy one (#3) for now.

Signed-off-by: Vegard Nossum <vegard.nossum@xxxxxxxxx>


---
 arch/x86/Kconfig.debug |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug
index 1067ad7..de186c5 100644
--- a/arch/x86/Kconfig.debug
+++ b/arch/x86/Kconfig.debug
@@ -279,6 +279,7 @@ menuconfig KMEMCHECK
 	depends on (SLUB && !SLUB_DEBUG_ON) || (SLAB && !DEBUG_SLAB)
 	depends on !CC_OPTIMIZE_FOR_SIZE
 	depends on !DEBUG_PAGEALLOC
+	depends on !FUNCTION_TRACER
 	select FRAME_POINTER
 	select STACKTRACE
 	default n
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Stable Commits]     [Linux Stable Kernel]     [Linux Kernel]     [Linux USB Devel]     [Linux Video &Media]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux