diff options
| author | Jason Wessel <jason.wessel@windriver.com> | 2012-03-23 09:35:05 -0500 |
|---|---|---|
| committer | Jason Wessel <jason.wessel@windriver.com> | 2012-03-29 17:41:25 -0500 |
| commit | 3751d3e85cf693e10e2c47c03c8caa65e171099b (patch) | |
| tree | 65d123dac17103f6862831bcb4271b263805fd9f /include | |
| parent | 98b54aa1a2241b59372468bd1e9c2d207bdba54b (diff) | |
| download | linux-3751d3e85cf693e10e2c47c03c8caa65e171099b.tar.bz2 | |
x86,kgdb: Fix DEBUG_RODATA limitation using text_poke()
There has long been a limitation using software breakpoints with a
kernel compiled with CONFIG_DEBUG_RODATA going back to 2.6.26. For
this particular patch, it will apply cleanly and has been tested all
the way back to 2.6.36.
The kprobes code uses the text_poke() function which accommodates
writing a breakpoint into a read-only page. The x86 kgdb code can
solve the problem similarly by overriding the default breakpoint
set/remove routines and using text_poke() directly.
The x86 kgdb code will first attempt to use the traditional
probe_kernel_write(), and next try using a the text_poke() function.
The break point install method is tracked such that the correct break
point removal routine will get called later on.
Cc: x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: stable@vger.kernel.org # >= 2.6.36
Inspried-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Diffstat (limited to 'include')
| -rw-r--r-- | include/linux/kgdb.h | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/include/linux/kgdb.h b/include/linux/kgdb.h index e5d689c1d774..c4d2fc194ede 100644 --- a/include/linux/kgdb.h +++ b/include/linux/kgdb.h @@ -63,7 +63,8 @@ enum kgdb_bptype { BP_HARDWARE_BREAKPOINT, BP_WRITE_WATCHPOINT, BP_READ_WATCHPOINT, - BP_ACCESS_WATCHPOINT + BP_ACCESS_WATCHPOINT, + BP_POKE_BREAKPOINT, }; enum kgdb_bpstate { |