LKML Archive on
help / color / mirror / Atom feed
From: Jarek Poplawski <>
Cc: Ingo Molnar <>
Subject: [PATCH] lockdep: debug_locks check after check_chain_key
Date: Mon, 12 Feb 2007 14:47:53 +0100	[thread overview]
Message-ID: <20070212134753.GA7737@ff.dom.local> (raw)

In __lock_acquire check_chain_key can turn off
debug_locks, so check is needed to assure proper
return code.

Signed-off-by: Jarek Poplawski <>


diff -Nurp linux-2.6.20-git7-/kernel/lockdep.c linux-2.6.20-git7/kernel/lockdep.c
--- linux-2.6.20-git7-/kernel/lockdep.c	2007-02-12 13:13:15.000000000 +0100
+++ linux-2.6.20-git7/kernel/lockdep.c	2007-02-12 14:18:31.000000000 +0100
@@ -2228,6 +2228,10 @@ out_calc_hash:
+	if (unlikely(!debug_locks))
+		return 0;
 	if (unlikely(curr->lockdep_depth >= MAX_LOCK_DEPTH)) {
 		printk("BUG: MAX_LOCK_DEPTH too low!\n");

                 reply	other threads:[~2007-02-12 13:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070212134753.GA7737@ff.dom.local \ \ \ \
    --subject='Re: [PATCH] lockdep: debug_locks check after check_chain_key' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).