From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Date: Wed, 30 Mar 2016 19:19:21 +0200
From: Peter Zijlstra <peterz@infradead.org>
To: Alfredo Alvarez Fernandez <alfredoalvarezfernandez@gmail.com>
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: <CA+icZUUvEWoAQUUXPxPxzb-Y7ajuLOJqXFF2sfR1iBbQu0yBoA@mail.gmail.com>
 <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>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-fsdevel.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!