From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758898Ab1BPKQT (ORCPT ); Wed, 16 Feb 2011 05:16:19 -0500 Received: from mx1.redhat.com ([209.132.183.28]:45844 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755944Ab1BPKQQ (ORCPT ); Wed, 16 Feb 2011 05:16:16 -0500 Date: Wed, 16 Feb 2011 11:15:21 +0100 From: Andrea Arcangeli To: Peter Zijlstra Cc: Thomas Gleixner , Jeremy Fitzhardinge , "H. Peter Anvin" , the arch/x86 maintainers , "Xen-devel@lists.xensource.com" , Linux Kernel Mailing List , Ian Campbell , Jan Beulich , Larry Woodman , Andrew Morton , Andi Kleen , Johannes Weiner , Hugh Dickins , Rik van Riel Subject: Re: [PATCH] fix pgd_lock deadlock Message-ID: <20110216101521.GU5935@random.random> References: <20110207232045.GJ3347@random.random> <20110215190710.GL5935@random.random> <20110215195450.GO5935@random.random> <20110215225234.GP5935@random.random> <20110215231733.GR5935@random.random> <1297850294.2413.30.camel@twins> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1297850294.2413.30.camel@twins> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 16, 2011 at 10:58:14AM +0100, Peter Zijlstra wrote: > On Wed, 2011-02-16 at 00:17 +0100, Andrea Arcangeli wrote: > > On Wed, Feb 16, 2011 at 12:03:30AM +0100, Thomas Gleixner wrote: > > > I assume you run it with a lockdep enabled kernel as well, right ? > > > > Yes, I always run with lockdep and prove locking enabled on my test > > box, not sure how it's meant to trigger more bugs in this case, the > > debug check that should be relevant for this is DEBUG_VM and that is > > enabled too of course. I didn't try DEBUG_PAGEALLOC yet. > > I think what Thomas tried to tell you is that your > VM_BUG_ON(in_interrupt()) is fully redundant if you have lockdep > enabled. > > Lockdep will warn you if a !irqsave lock is taken from IRQ context, > since that is a clear inversion problem. Ah I get it now, but I prefer to have it on an all my builds, and I don't keep lockdep on for all builds (but I keep DEBUG_VM on). It's still only debug code that no production system will ever deal with, so it should be good to exercise it in more than on debug .config considering it's very low overhead (pgd_lock is never taken in fast paths) so it's suitable for a VM_BUG_ON.