public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <ebb9@byu.net>
To: ctrn3e8 <ctrn3e8@gmail.com>
Cc: =?ISO-8859-1?Q?Jean-Pie?=@oss.sgi.com,
	"Miklos Szeredi" <miklos@szeredi.hu>,
	fuse-devel@lists.sourceforge.net,
	bug-coreutils <bug-coreutils@gnu.org>,
	"rre André" <jean-pierre.andre@wanadoo.fr>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	xfs@oss.sgi.com, "Christoph Hellwig" <hch@lst.de>,
	"OGAWA Hirofumi" <hirofumi@mail.parknet.co.jp>
Subject: Re: [fuse-devel] utimensat fails to update ctime
Date: Wed, 23 Dec 2009 17:50:04 -0700	[thread overview]
Message-ID: <4B32BABC.7020908@byu.net> (raw)
In-Reply-To: <4B32B303.6070807@gmail.com>

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

  reply	other threads:[~2009-12-24  0:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B2B156D.9040604@byu.net>
     [not found] ` <87aaxclr4q.fsf@devron.myhome.or.jp>
     [not found]   ` <4B2F7421.10005@byu.net>
     [not found]     ` <4B2F7A95.3010708@byu.net>
2009-12-21 15:05       ` utimensat fails to update ctime OGAWA Hirofumi
2009-12-22  4:37         ` Eric Blake
2009-12-22  9:00           ` OGAWA Hirofumi
2009-12-22  9:56             ` [fuse-devel] " Jean-Pierre André
2009-12-22 10:43               ` OGAWA Hirofumi
2009-12-22 12:07                 ` Jean-Pierre André
2009-12-22 13:00                   ` Miklos Szeredi
2009-12-22 13:30                   ` OGAWA Hirofumi
2009-12-22 16:16                     ` Jean-Pierre André
2009-12-22 17:58                       ` OGAWA Hirofumi
2009-12-23  9:43                         ` Jean-Pierre André
2009-12-23 11:08                           ` OGAWA Hirofumi
2009-12-23 12:54                         ` Eric Blake
2009-12-23 19:23                           ` OGAWA Hirofumi
2009-12-24  0:17                           ` ctrn3e8
2009-12-24  0:50                             ` Eric Blake [this message]
2009-12-23 14:28                         ` Jean-Pierre André
2009-12-22 12:34           ` Dave Chinner
2009-12-22 12:42             ` Eric Blake
2009-12-23  7:53               ` Christoph Hellwig
2009-12-22 17:45         ` Christoph Hellwig
2009-12-22 19:06           ` OGAWA Hirofumi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B32BABC.7020908@byu.net \
    --to=ebb9@byu.net \
    --cc==?ISO-8859-1?Q?Jean-Pie?=@oss.sgi.com \
    --cc=bug-coreutils@gnu.org \
    --cc=ctrn3e8@gmail.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=hch@lst.de \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jean-pierre.andre@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox