Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264271AbTGIRkq (ORCPT ); Wed, 9 Jul 2003 13:40:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264312AbTGIRkq (ORCPT ); Wed, 9 Jul 2003 13:40:46 -0400 Received: from lindsey.linux-systeme.com ([80.190.48.67]:21254 "EHLO mx00.linux-systeme.com") by vger.kernel.org with ESMTP id S264271AbTGIRkp (ORCPT ); Wed, 9 Jul 2003 13:40:45 -0400 From: Marc-Christian Petersen Organization: Working Overloaded Linux Kernel To: Marcelo Tosatti Subject: Re: ->direct_IO API change in current 2.4 BK Date: Wed, 9 Jul 2003 19:55:08 +0200 User-Agent: KMail/1.5.2 Cc: Andreas Dilger , Andrea Arcangeli , Christoph Hellwig , marcelo@connectiva.com.br, Trond Myklebust , lkml References: <20030709133109.A23587@infradead.org> <200307091943.13680.m.c.p@wolk-project.de> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200307091954.12895.m.c.p@wolk-project.de> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 827 Lines: 22 On Wednesday 09 July 2003 19:46, Marcelo Tosatti wrote: Hi Marcelo, > > > > > I just got a nice XFS oops due to the direct_IO API change in > > > > > 2.4. Guys, this is a STABLE series and APIs are supposed to be > > > > > exactly that, _STABLE_. If you really think O_DIRECT on NFS is soo > > > > > important please add a ->direct_IO2 for NFS like the reiserfs > > > > > read_inode2 hack. > > > > I wonder why -aa and -wolk don't have these problems with O_DIRECT vs. > > XFS. > Do they have the NFS DIRECT IO patch? Yes. If not, my sentence would be superflous ;) ciao, Marc - 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/