From: Andrea Arcangeli Subject: Re: [PATCH] fix pgd_lock deadlock Date: Wed, 16 Feb 2011 00:17:33 +0100 Message-ID: <20110215231733.GR5935@random.random> References: <20110204012109.GP5843@random.random> <4D4C6F45.6010204@goop.org> <20110207232045.GJ3347@random.random> <20110215190710.GL5935@random.random> <20110215195450.GO5935@random.random> <20110215225234.GP5935@random.random> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Thomas Gleixner Cc: 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 List-Id: xen-devel@lists.xenproject.org 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.