Re: [fuse-devel] utimensat fails to update ctime

[Eric Blake <ebb9@byu.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to ctrn3e8 on 12/23/2009 5:17 PM:
> The strace has the following function call  (and it may be because I am
> looking at the trace rather than the actual source):

> utimensat(0, NULL, {UTIME_OMIT, UTIME_NOW}, 0) = 0

> The two don't seem to match.  Is this just because of the way the trace is printed?

Yes.  When the tv_nsec field is UTIME_OMIT or UTIME_NOW, the tv_sec field
is irrelevant.  Therefore, to save on space, strace omits the tv_sec field
in its output.  But rest assured that the kernel has read access to all
four 32-bit words located at the timespec pointer passed in the syscall.

> No mention of ntfs-3g support for nanosecond time stamping.

Read the rest of the thread on lkml - that is a known issue, which will
probably not be solved any sooner than January (all the patches this week
only dealt with mishandling of UTIME_OMIT).

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

iEYEARECAAYFAksyurwACgkQ84KuGfSFAYDJ2gCgv9YMVwl7HL//ThRvQKJH5hSR
S/EAn0WzRr7FrFbkDHUtEfRdtXDdkqxT
=YpCl
-----END PGP SIGNATURE-----

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs