From mboxrd@z Thu Jan  1 00:00:00 1970
From: Roman Zippel <zippel@linux-m68k.org>
Subject: Re: ctime/mtime update in affs and hpfs write path
Date: Tue, 1 Nov 2005 02:03:29 +0100 (CET)
Message-ID: <Pine.LNX.4.61.0511010200490.1386@scrub.home>
References: <20051031235306.GA21218@lst.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: linux-fsdevel@vger.kernel.org, mikulas@artax.karlin.mff.cuni.cz
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from scrub.xs4all.nl ([194.109.195.176]:24497 "EHLO scrub.xs4all.nl")
	by vger.kernel.org with ESMTP id S964864AbVKABDo (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Mon, 31 Oct 2005 20:03:44 -0500
To: Christoph Hellwig <hch@lst.de>
In-Reply-To: <20051031235306.GA21218@lst.de>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

Hi,

On Tue, 1 Nov 2005, Christoph Hellwig wrote:

> 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?

For affs I don't really know, my best guess is it has been there forever 
and there never was a reason to remove it.

bye, Roman