From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [LOCKDEP] xfs: possible recursive locking detected Date: 04 Jul 2006 14:42:42 +0200 Message-ID: References: <20060704004116.GA7612@martell.zuzino.mipt.ru> <20060704011858.GG1605@parisc-linux.org> <20060704112503.H1495869@wobbly.melbourne.sgi.com> <20060704063225.GA2752@elte.hu> <20060704084143.GA12931@elte.hu> <20060704191100.C1497438__38681.8935432986$1152004607$gmane$org@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Alexey Dobriyan , Matthew Wilcox , linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com, Arjan van de Ven , mingo@elte.hu Return-path: Received: from mx1.suse.de ([195.135.220.2]:9444 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S932248AbWGDMnI (ORCPT ); Tue, 4 Jul 2006 08:43:08 -0400 To: Nathan Scott In-Reply-To: <20060704191100.C1497438__38681.8935432986$1152004607$gmane$org@wobbly.melbourne.sgi.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Nathan Scott writes: > > That would be good, but it doesn't work for all situations > unfortunately, and it would loose that debug-kernel sanity > checking that we have in there which validates ilock/iolock > ordering rules. Isn't that obsolete now with lockdep? -Andi