From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Fasheh Subject: Re: [ANNOUNCE] new new aops patchset Date: Wed, 4 Apr 2007 16:17:20 -0700 Message-ID: <20070404231720.GI21982@ca-server1.us.oracle.com> References: <20070402120934.GA19626@wotan.suse.de> <20070404221034.GF21982@ca-server1.us.oracle.com> <1175727919.5019.14.camel@dyn9047017100.beaverton.ibm.com> Reply-To: Mark Fasheh Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Nick Piggin , Linux Filesystems , Steven Whitehouse To: Badari Pulavarty Return-path: Received: from rgminet01.oracle.com ([148.87.113.118]:34986 "EHLO rgminet01.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752701AbXDDXRc (ORCPT ); Wed, 4 Apr 2007 19:17:32 -0400 Content-Disposition: inline In-Reply-To: <1175727919.5019.14.camel@dyn9047017100.beaverton.ibm.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Apr 04, 2007 at 04:05:19PM -0700, Badari Pulavarty wrote: > Hmm.. Okay, only filesystems that could return AOP_TRUNCATED_PAGE > are ocf2 and gfs2. Now that both of them are switched to have > write_begin()/write_end(), why do we need this code to handle > AOP_TRUNCATED_PAGE (in the else part) ? Can't we just cleanup/nuke > all the AOP_TRUNCATED_PAGE handling ? We don't - I'm pretty sure that fs-no-AOP_TRUNCATED_PAGE.patch gets rid of them. --Mark -- Mark Fasheh Senior Software Developer, Oracle mark.fasheh@oracle.com