diff options
| author | Jason Wessel <jason.wessel@windriver.com> | 2010-11-15 15:07:35 +0100 |
|---|---|---|
| committer | Jason Wessel <jason.wessel@windriver.com> | 2010-11-17 20:54:57 +0100 |
| commit | 10a6e67648d4b47769953bd24759ba9609bf00df (patch) | |
| tree | 87a7381db182f858bda6b275c421ee01f674b5de /arch/x86/kernel/dumpstack_64.c | |
| parent | kdb: fix crash when KDB_BASE_CMD_MAX is exceeded (diff) | |
| download | linux-10a6e67648d4b47769953bd24759ba9609bf00df.tar.xz linux-10a6e67648d4b47769953bd24759ba9609bf00df.zip | |
kgdb,x86: fix regression in detach handling
The fix from ba773f7c510c0b252145933926c636c439889207
(x86,kgdb: Fix hw breakpoint regression) was not entirely complete.
The kgdb_remove_all_hw_break() function also needs to call the
hw_break_release_slot() or else a breakpoint can get activated again
after the debugger has detached.
The kgdb test suite exposes the behavior in the form of either a hang
or repetitive failure. The kernel config that exposes the problem
contains all of the following:
CONFIG_DEBUG_RODATA=y
CONFIG_KGDB_TESTS=y
CONFIG_KGDB_TESTS_ON_BOOT=y
CONFIG_KGDB_TESTS_BOOT_STRING="V1F100"
Reported-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Tested-by: Frederic Weisbecker <fweisbec@gmail.com>
Diffstat (limited to 'arch/x86/kernel/dumpstack_64.c')
0 files changed, 0 insertions, 0 deletions