summaryrefslogtreecommitdiffstats
path: root/lib/debug_locks.c
diff options
context:
space:
mode:
authorFrederic Weisbecker <fweisbec@gmail.com>2009-04-11 03:17:17 +0200
committerIngo Molnar <mingo@elte.hu>2009-04-12 16:10:51 +0200
commit9eeba6138cefc0435695463ddadb0d95e0a6bcd2 (patch)
treedaba646e5ddd27132e9679aa3eabec389bf4722e /lib/debug_locks.c
parent066123a535927b3f17cac2305258cc71abdb0d92 (diff)
downloadop-kernel-dev-9eeba6138cefc0435695463ddadb0d95e0a6bcd2.zip
op-kernel-dev-9eeba6138cefc0435695463ddadb0d95e0a6bcd2.tar.gz
lockdep: warn about lockdep disabling after kernel taint
Impact: provide useful missing info for developers Kernel taint can occur in several situations such as warnings, load of prorietary or staging modules, bad page, etc... But when such taint happens, a developer might still be working on the kernel, expecting that lockdep is still enabled. But a taint disables lockdep without ever warning about it. Such a kernel behaviour doesn't really help for kernel development. This patch adds this missing warning. Since the taint is done most of the time after the main message that explain the real source issue, it seems safe to warn about it inside add_taint() so that it appears at last, without hurting the main information. v2: Use a generic helper to disable lockdep instead of an open coded xchg(). Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com> Cc: Peter Zijlstra <peterz@infradead.org> LKML-Reference: <1239412638-6739-1-git-send-email-fweisbec@gmail.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'lib/debug_locks.c')
-rw-r--r--lib/debug_locks.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/debug_locks.c b/lib/debug_locks.c
index 0218b46..bc3b117 100644
--- a/lib/debug_locks.c
+++ b/lib/debug_locks.c
@@ -36,7 +36,7 @@ int debug_locks_silent;
*/
int debug_locks_off(void)
{
- if (xchg(&debug_locks, 0)) {
+ if (__debug_locks_off()) {
if (!debug_locks_silent) {
oops_in_progress = 1;
console_verbose();
OpenPOWER on IntegriCloud