From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932852AbcC3RT1 (ORCPT ); Wed, 30 Mar 2016 13:19:27 -0400 Received: from casper.infradead.org ([85.118.1.10]:54860 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753575AbcC3RTZ (ORCPT ); Wed, 30 Mar 2016 13:19:25 -0400 Date: Wed, 30 Mar 2016 19:19:21 +0200 From: Peter Zijlstra To: Alfredo Alvarez Fernandez Cc: sedat.dilek@gmail.com, mingo@kernel.org, torvalds@linux-foundation.org, tytso@mit.edu, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] lockdep: print chain_key collision information Message-ID: <20160330171921.GC3408@twins.programming.kicks-ass.net> References: <1459357416-19190-1-git-send-email-alfredoalvarezernandez@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1459357416-19190-1-git-send-email-alfredoalvarezernandez@gmail.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 30, 2016 at 07:03:36PM +0200, Alfredo Alvarez Fernandez wrote: > A sequence of pairs [class_idx -> corresponding chain_key iteration] > is printed for both the current held_lock chain and the cached chain. > That exposes the two different class_idx sequences that led to that > particular hash value. Nice, thanks!