Chung-Chiang Cheng <shepjeng@xxxxxxxxx> writes: > I got your point. Correctly speaking ctime is not really dropped but mixed > with mtime after my patch. They share the same field on disk. Before that > ctime is mixed with crtime. > > I choose this new behavior because ctime and mtime are similar concepts. > ctime is the update time for file attributes, and mtime is the one for file > contents. They are updated together most of the time with few exceptions > (rename, rmdir, unlink) in the current FAT implementation. No, a user can change the ctime to arbitrary time, and after the your patch, the changed ctime only hold on a memory inode. So a user sees ctime jump backward and forward when a memory inode is expired. (Of course, this happens just by "cp -a" in real world use case.) I'm pointing about this introduced new behavior by your patch. Thanks. -- OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx>
