From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752080AbcC0MDr (ORCPT ); Sun, 27 Mar 2016 08:03:47 -0400 Received: from mail-io0-f171.google.com ([209.85.223.171]:34032 "EHLO mail-io0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751562AbcC0MDq (ORCPT ); Sun, 27 Mar 2016 08:03:46 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 27 Mar 2016 05:03:44 -0700 X-Google-Sender-Auth: Bo_2qRDDqdVm9a0nehK9k0siy9Q Message-ID: Subject: Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260 From: Linus Torvalds To: Sedat Dilek , Ingo Molnar , Peter Zijlstra Cc: "Theodore Ts'o" , linux-fsdevel , LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Mar 27, 2016 at 1:57 AM, Sedat Dilek wrote: > > I pulled ext4.git#dev on top of Linux v4.6-rc1... > > ... and did not see the call-trace. Unless you're using overlayfs or per-file encryption, I'm not seeing that any of that should make any difference (but it's entirely possible I'm missing something). Was it entirely repeatable before? Maybe it just happened to happen without that update, and then happened to _not_ happen after you rebooted with that 'dev' branch pulled in? 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. Linus