From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] Turn do_sync_file_range() into do_sync_mapping_range() Date: Wed, 21 Mar 2007 14:44:26 +0000 Message-ID: <20070321144426.GA25213@infradead.org> References: <20070320214626.GC23274@ca-server1.us.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, hch@infradead.org, viro@ftp.linux.org.uk To: Mark Fasheh Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:58839 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752923AbXCUOot (ORCPT ); Wed, 21 Mar 2007 10:44:49 -0400 Content-Disposition: inline In-Reply-To: <20070320214626.GC23274@ca-server1.us.oracle.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, Mar 20, 2007 at 02:46:26PM -0700, Mark Fasheh wrote: > do_sync_file_range() accepts a file * from which it takes an address_space > to sync. Abstract out the bulk of the function into do_sync_mapping_range() > which takes the address_space directly. This way callers who want to sync an > address_space directly can take advantage of the functionality provided. > > do_sync_file_range() is preserved as a 3 line wrapper around > do_sync_mapping_range(). > > Ocfs2 in particular would like to use this to initiate a sync of a specific > inode range during truncate, where a file * may not be available. Looks good to me, but I agree with Andrew that we should simply kill do_sync_file_range, espcially as at least one of the callers has file->f_mapping guaranteed != NULL;