public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jean-Pierre André" <jean-pierre.andre@wanadoo.fr>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Eric Blake <ebb9@byu.net>,
	fuse-devel@lists.sourceforge.net,
	Miklos Szeredi <miklos@szeredi.hu>,
	Christoph Hellwig <hch@lst.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: [fuse-devel] utimensat fails to update ctime
Date: Tue, 22 Dec 2009 10:56:20 +0100	[thread overview]
Message-ID: <4B3097C4.3060803@wanadoo.fr> (raw)
In-Reply-To: <87d427jscr.fsf@devron.myhome.or.jp>

Hi all,


OGAWA Hirofumi wrote:
> Eric Blake<ebb9@byu.net>  writes:
>
>    
> It is likely the issue of libfuse or ntfs-3g. I don't know about ntfs-3g
> people at all. So, for now, just Cc: to fuse people.
>    

Which ntfs-3g version are you using ?

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

Currently ntfs-3g does not set sub-second precision.

There is also a slight problem in the fuse interface :
the time buffer is never passed as NULL, consequently
in some circumstances ntfs-3g cannot decide correctly
over permissions. A permissive action is taken in this
situation.

> > From this, "ia_valid" will have "ATTR_CTIME | ATTR_MTIME". And the
> request would pass to userland via fuse of kernel part, then it will be
> handled by libfuse.
>
> > From quick grep of libfuse and ntfs-3g (would not be latest), ntfs-3g is
> using "struct fuse_operations", not "struct fuse_lowlevel_ops".
>    

With the latest ntfs-3g, currently as a release candidate,
you can (optionally) use the low level fuse interface
http://pagesperso-orange.fr/b.andre/advanced-ntfs-3g.html
use the "lowntfs-3g" driver instead of "ntfs-3g"

Hope this helps

Regards

Jean-Pierre




  reply	other threads:[~2009-12-22 10:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  5:38 utimensat fails to update ctime Eric Blake
2009-12-21  7:31 ` OGAWA Hirofumi
2009-12-21 13:12   ` Eric Blake
2009-12-21 13:39     ` Eric Blake
2009-12-21 15:05       ` OGAWA Hirofumi
2009-12-22  4:37         ` Eric Blake
2009-12-22  9:00           ` OGAWA Hirofumi
2009-12-22  9:56             ` Jean-Pierre André [this message]
2009-12-22 10:43               ` [fuse-devel] " 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
     [not found]                           ` <4B32B303.6070807@gmail.com>
2009-12-24  0:50                             ` Eric Blake
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=4B3097C4.3060803@wanadoo.fr \
    --to=jean-pierre.andre@wanadoo.fr \
    --cc=ebb9@byu.net \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=hch@lst.de \
    --cc=hirofumi@mail.parknet.co.jp \
    --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