Messages in this thread | | | Date | Wed, 23 Dec 2009 05:54:05 -0700 | From | Eric Blake <> | Subject | Re: [fuse-devel] utimensat fails to update ctime |
| |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
According to OGAWA Hirofumi on 12/22/2009 10:58 AM: >> I suggest I port Miklos patch to fuse-lite soon, >> and delay the low-level case (and microsecond >> precision) until January. Does that suit your needs ? > > Thanks. Sounds good. I'm not using ntfs-3g actually, I just bridged the > bug report on lkml to others. Eric?
I'm also bridging the report from a coreutils user (now cc'd). Since I also don't use ntfs-3g, I'm hoping that ctrn3e8 will be able to help test whether the latest patch to ntfs-3g makes a difference in properly setting times. To me, delaying precision while fixing UTIME_OMIT semantics is a reasonable approach.
By the way, is there any reliable way, other than uname() and checking for a minimum kernel version, to tell if all file systems will properly support UTIME_OMIT? For coreutils 8.3, we will be inserting a workaround where instead of using UTIME_OMIT, we call fstatat() in advance of utimensat() and pass the original timestamp down. But it would be nice to avoid the penalty of the extra stat if there were a reliable way to ensure that, regardless of file system, the use of UTIME_OMIT will be honored. After all, coreutils wants touch(1) to work regardless of how old the user's kernel and file system drivers are.
- -- Don't work too hard, make some time for fun as well!
Eric Blake ebb9@byu.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAksyEu0ACgkQ84KuGfSFAYCrzACgirIjqmS7vFOBcI8xau6jHEa0 4L0AnAjJkje+tSMF/FZkTbkohg/fhQ+i =ngx0 -----END PGP SIGNATURE-----
| |