Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932119AbWE3Bey (ORCPT ); Mon, 29 May 2006 21:34:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932103AbWE3BbR (ORCPT ); Mon, 29 May 2006 21:31:17 -0400 Received: from smtp.osdl.org ([65.172.181.4]:40128 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S932095AbWE3BaO (ORCPT ); Mon, 29 May 2006 21:30:14 -0400 Date: Mon, 29 May 2006 18:34:04 -0700 From: Andrew Morton To: Ingo Molnar Cc: linux-kernel@vger.kernel.org, arjan@infradead.org Subject: Re: [patch 16/61] lock validator: fown locking workaround Message-Id: <20060529183404.48878079.akpm@osdl.org> In-Reply-To: <20060529212423.GP3155@elte.hu> References: <20060529212109.GA2058@elte.hu> <20060529212423.GP3155@elte.hu> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.17; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 675 Lines: 16 On Mon, 29 May 2006 23:24:23 +0200 Ingo Molnar wrote: > temporary workaround for the lock validator: make all uses of > f_owner.lock irq-safe. (The real solution will be to express to > the lock validator that f_owner.lock rules are to be generated > per-filesystem.) This description forgot to tell us what problem is being worked around. This patch is a bit of a show-stopper. How hard-n-bad is the real fix? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/