Prev: [PATCH 07/17] gdbstub: Implement gdbserial 'p' and 'P' packets
Next: [PATCH 16/17] kgdb,x86: use macro HBP_NUM to replace magic number 4
From: Jason Wessel on 5 Aug 2010 10:50
The kdb kmap should never get used outside of the kernel debugger
exception context.

Signed-off-by: Jason Wessel<jason.wessel(a)windriver.com>
CC: Andrew Morton <akpm(a)linux-foundation.org>
CC: Ingo Molnar <mingo(a)elte.hu>
CC: linux-mm(a)kvack.org
---
mm/highmem.c | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/mm/highmem.c b/mm/highmem.c
index 66baa20..7a0aa1b 100644
--- a/mm/highmem.c
+++ b/mm/highmem.c
@@ -26,6 +26,7 @@
#include <linux/init.h>
#include <linux/hash.h>
#include <linux/highmem.h>
+#include <linux/kgdb.h>
#include <asm/tlbflush.h>

/*
@@ -470,6 +471,12 @@ void debug_kmap_atomic(enum km_type type)
warn_count--;
}
}
+#ifdef CONFIG_KGDB_KDB
+ if (unlikely(type == KM_KDB && atomic_read(&kgdb_active) == -1)) {
+ WARN_ON(1);
+ warn_count--;
+ }
+#endif /* CONFIG_KGDB_KDB */
}

#endif
--
1.6.3.3

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 07/17] gdbstub: Implement gdbserial 'p' and 'P' packets
Next: [PATCH 16/17] kgdb,x86: use macro HBP_NUM to replace magic number 4