-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Simon Josefsson on 11/2/2009 4:04 AM: >>> I can't reproduce on current debian testing, so it is likely an old bug. >> The Linux man pages are explicit that older kernels had a bug where >> UTIME_OMIT with a non-zero seconds field failed with EINVAL instead of >> working, but I thought my code path already worked around this. > > Errno is EINVAL. I can single-step if the other information in this > e-mail isn't sufficient, let me know. > >> Also, an strace run would be invaluable, to see what actual arguments were >> passed to the syscall. > > Attached.
And it only lists syscall_280. Not very helpful - it means strace is so old that it doesn't recognize the utimensat syscall or how to display its arguments. I'm starting to think, however, that this probably means there was a time when utimesnat existed but did not support UTIME_OMIT (whereas the current code only works around the problem where utimensat exists and knows about UTIME_OMIT but rejects non-zero seconds). If I'm right (and single stepping through it once I get access to the machine will let me know), then I can work around it in the same way we implement UTIME_OMIT for futimesat (where UTIME_OMIT has never been supported). - -- Don't work too hard, make some time for fun as well! Eric Blake e...@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/ iEYEARECAAYFAkrvpA8ACgkQ84KuGfSFAYBJCgCfZ7wsag49bCpkRvuF9cwIbGZE YycAoIBaqawW9GH9trl+Pg5QELyyNd+v =/Kz0 -----END PGP SIGNATURE-----
