From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoph Hellwig <hch@lst.de>
Subject: ctime/mtime update in affs and hpfs write path
Date: Tue, 1 Nov 2005 00:53:06 +0100
Message-ID: <20051031235306.GA21218@lst.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from verein.lst.de ([213.95.11.210]:12455 "EHLO mail.lst.de")
	by vger.kernel.org with ESMTP id S964895AbVJaXxL (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Mon, 31 Oct 2005 18:53:11 -0500
To: linux-fsdevel@vger.kernel.org, mikulas@artax.karlin.mff.cuni.cz,
	zippel@linux-m68k.org
Content-Disposition: inline
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

Both AFFS and HPFS update the ctime and mtime in the write path, after
generic_file_write returned and mark the inode dirty.  Anyone's got an
idea why these two filesystems aren't happy with the ctime/mtime updates
vi generic_file_write before we copied the data into the pagecache?