From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752453AbcC0UsP (ORCPT ); Sun, 27 Mar 2016 16:48:15 -0400 Received: from casper.infradead.org ([85.118.1.10]:43051 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751298AbcC0UsN (ORCPT ); Sun, 27 Mar 2016 16:48:13 -0400 Date: Sun, 27 Mar 2016 22:48:10 +0200 From: Peter Zijlstra To: Linus Torvalds Cc: Sedat Dilek , Ingo Molnar , "Theodore Ts'o" , linux-fsdevel , LKML Subject: Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260 Message-ID: <20160327204810.GW6356@twins.programming.kicks-ass.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Sun, Mar 27, 2016 at 05:03:44AM -0700, Linus Torvalds wrote: > Anyway, I don't think that DEBUG_LOCKS_WARN_ON() in > > kernel/locking/lockdep.c:2017 __lock_acquire > > would be an ext4 issue, it looks more like an internal lockdep issue. > > Adding in the lockdep people, who will set me right. You are right; this is lockdep running into a hash collision; which is a new DEBUG_LOCKDEP test. See 9e4e7554e755 ("locking/lockdep: Detect chain_key collisions").