Arjan van de Ven wrote:
quoted text
> On Tue, 6 Nov 2007 18:19:45 +0100
> Jan Kara <jack@suse.cz> wrote:
> 
>> Implement recursive mtime (rtime) feature for ext3. The feature works
>> as follows: In each directory we keep a flag EXT3_RTIME_FL
>> (modifiable by a user) whether rtime should be updated. In case a
>> directory or a file in it is modified and when the flag is set,
>> directory's rtime is updated, the flag is cleared, and we move to the
>> parent. If the flag is set there, we clear it, update rtime and
>> continue upwards upto the root of the filesystem. In case a regular
>> file or symlink is modified, we pick arbitrary of its parents
>> (actually the one that happens to be at the head of i_dentry list)
>> and start the rtime update algorith there.
> 
> Ok since mtime (and rtime) are part of the inode and not the dentry...
> how do you deal with hardlinks? And with cases of files that have been
> unlinked? (ok the later is a wash obviously other than not crashing)
> 

There is only one possible answer... he only updates the directory path 
that was used to touch the particular file involved.  Thus, the 
semantics gets grotty not just in the presence of hard links, but also 
in the presence of bind- and other non-root mounts.

	-hpa
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/