From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: [PATCH 2/2] introduce I_SYNC Date: Tue, 8 May 2007 14:00:40 +0200 Message-ID: <20070508120037.GB20637@lazybastard.org> References: <20070507215913.GA15054@lazybastard.org> <20070507220142.GC15054@lazybastard.org> <1178609028.3042.275.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Andrew Morton , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Dave Kleikamp , David Chinner To: Thomas Gleixner Return-path: Content-Disposition: inline In-Reply-To: <1178609028.3042.275.camel@localhost.localdomain> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, 8 May 2007 09:23:48 +0200, Thomas Gleixner wrote: > On Tue, 2007-05-08 at 00:01 +0200, J=C3=B6rn Engel wrote: > > This patch is actually independent of LogFS. It fixes a deadlock > > hidden in fs/fs-writeback.c that LogFS was unlucky enough to trigge= r. > > I strongly suspect NTFS triggered the same deadlock and "solved" it= by > > introducing iget5_nowait(). For LogFS, iget5_nowait() would transl= ate > > the deadlock into data corruption, so that is not an option. >=20 > Have you talked to NTFS folks about that ? Anton was on Cc: when I sent the first round of this patch. He didn't respond. > If it is a general problem, then please seperate the patch from logfs= =2E The problem certainly is generic and the patch already seperate. I can resend it in a seperate thread if that is preferred. Until yesterday it appeared as if LogFS was the only code that could trigger the problem. NTFS is hard to judge without maintainer comment. By now it appears as if JFS and NFS have joined in. Maybe I was over-cautious in not sending it for some month. J=C3=B6rn --=20 He that composes himself is wiser than he that composes a book. -- B. Franklin