From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id n9FCCFYR009410 for ; Thu, 15 Oct 2009 07:12:18 -0500 Received: from bombadil.infradead.org (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 691181D7F49B for ; Thu, 15 Oct 2009 05:13:45 -0700 (PDT) Received: from bombadil.infradead.org (bombadil.infradead.org [18.85.46.34]) by cuda.sgi.com with ESMTP id 4iLnexkkSKwNHWt2 for ; Thu, 15 Oct 2009 05:13:45 -0700 (PDT) Date: Thu, 15 Oct 2009 08:13:45 -0400 From: Christoph Hellwig Subject: Re: deadlocks with fallocate Message-ID: <20091015121345.GA18234@infradead.org> References: <20091014150951.GA13123@infradead.org> <200910150758.06003.tneumann@users.sourceforge.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <200910150758.06003.tneumann@users.sourceforge.net> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Thomas Neumann Cc: Christoph Hellwig , linux-xfs@oss.sgi.com On Thu, Oct 15, 2009 at 07:58:05AM +0200, Thomas Neumann wrote: > I did some more tests, and indeed the patch makes the deadlock go away. Your > description of it as a hack makes me somewhat concerned about using it > permanently, but hopefully you will find a proper solution ;) It's basically a flag to say all allocations from this thread should not recurse back into filesystem code. I'll either need to change the allocations manually or keep this flag and write a comment documenting why. I'll decide what to on my long airplane ride tomorrow and will make sure it goes off to Linus' tree ASAP after that. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs