public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Gregory Haskins <ghaskins@novell.com>, stable <stable@kernel.org>,
	mingo@elte.hu, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [stable] [PATCH] lockdep: fix mismatched lockdep_depth/curr_chain_hash
Date: Mon, 8 Oct 2007 10:24:24 -0700	[thread overview]
Message-ID: <20071008172424.GA6692@kroah.com> (raw)
In-Reply-To: <1191576686.22357.64.camel@twins>

On Fri, Oct 05, 2007 at 11:31:26AM +0200, Peter Zijlstra wrote:
> 
> Stable team,
> 
> please consider this patch for the next 22-stable.

I don't see this patch in Linus's upstream tree.  We need it there to be
able to accept it for -stable.  Or is this just a bugfix of other things
that are already in his tree?

thanks,

greg k-h


> 
> ---
> Subject: lockdep: fix mismatched lockdep_depth/curr_chain_hash
> From: Gregory Haskins <ghaskins@novell.com>
> 
> It is possible for the current->curr_chain_key to become inconsistent with the
> current index if the chain fails to validate.  The end result is that future
> lock_acquire() operations may inadvertently fail to find a hit in the cache
> resulting in a new node being added to the graph for every acquire.
> 
> [ peterz: this might explain some of the lockdep is so _slow_ complaints. ]
> [ mingo: this does not impact the correctness of validation, but may slow
>   down future operations significantly, if the chain gets very long. ]
> 
> Signed-off-by: Gregory Haskins <ghaskins@novell.com>
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
>  kernel/lockdep.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: linux-2.6/kernel/lockdep.c
> ===================================================================
> --- linux-2.6.orig/kernel/lockdep.c
> +++ linux-2.6/kernel/lockdep.c
> @@ -2166,7 +2166,6 @@ out_calc_hash:
>  	}
>  #endif
>  	chain_key = iterate_chain_key(chain_key, id);
> -	curr->curr_chain_key = chain_key;
>  
>  	/*
>  	 * Trylock needs to maintain the stack of held locks, but it
> @@ -2215,6 +2214,7 @@ out_calc_hash:
>  		if (unlikely(!debug_locks))
>  			return 0;
>  
> +	curr->curr_chain_key = chain_key;
>  	curr->lockdep_depth++;
>  	check_chain_key(curr);
>  #ifdef CONFIG_DEBUG_LOCKDEP
> 
> 
> _______________________________________________
> stable mailing list
> stable@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/stable

  reply	other threads:[~2007-10-08 17:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05  4:03 [PATCH] LOCKDEP: fix mismatched lockdep_depth/curr_chain_hash Gregory Haskins
2007-10-05  9:31 ` [PATCH] lockdep: " Peter Zijlstra
2007-10-08 17:24   ` Greg KH [this message]
2007-10-08 17:36     ` [stable] " Peter Zijlstra
2007-10-08 17:39       ` Greg KH
2007-10-25 17:48         ` Peter Zijlstra
2007-10-25 18:55           ` Chuck Ebbert
2007-10-31 14:37             ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2007-10-31 15:03 Gregory Haskins
2007-10-31 15:44 Gregory Haskins
2007-10-31 16:24 ` [stable] " Greg KH

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20071008172424.GA6692@kroah.com \
    --to=greg@kroah.com \
    --cc=ghaskins@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=stable@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox