Re: ctime/mtime update in affs and hpfs write path

[Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>]

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?

In HPFS, there's no reason for mtime update --- just that it was left when 
porting code from older kernels. If generic_file_write updates it, you can 
remove update in HPFS.

As for inode dirty --- HPFS has its own dirty mechanism different from the 
kernel to avoid deadlocks (writing inode on HPFS needs to lock parent 
directory and you can't do it from ->write_inode method) --- let it be, it 
may be slower, but it's stable.

Mikulas