From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id nBMHvTHD146406 for ; Tue, 22 Dec 2009 11:57:29 -0600 Received: from mail.parknet.co.jp (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 9BD3711F216 for ; Tue, 22 Dec 2009 09:58:11 -0800 (PST) Received: from mail.parknet.co.jp (mail.parknet.co.jp [210.171.160.6]) by cuda.sgi.com with ESMTP id Z9pClAsv5prDBrRQ for ; Tue, 22 Dec 2009 09:58:11 -0800 (PST) From: OGAWA Hirofumi Subject: Re: [fuse-devel] utimensat fails to update ctime References: <4B2B156D.9040604@byu.net> <87aaxclr4q.fsf@devron.myhome.or.jp> <4B2F7421.10005@byu.net> <4B2F7A95.3010708@byu.net> <87hbrkjrk8.fsf@devron.myhome.or.jp> <4B304D04.6040501@byu.net> <87d427jscr.fsf@devron.myhome.or.jp> <4B3097C4.3060803@wanadoo.fr> <874onjjnln.fsf@devron.myhome.or.jp> <4B30B67A.7080703@wanadoo.fr> <87ljgvi1an.fsf@devron.myhome.or.jp> <4B30F0C9.2020702@wanadoo.fr> Date: Wed, 23 Dec 2009 02:58:03 +0900 In-Reply-To: <4B30F0C9.2020702@wanadoo.fr> ("Jean-Pierre =?iso-8859-1?Q?An?= =?iso-8859-1?Q?dr=E9=22's?= message of "Tue, 22 Dec 2009 17:16:09 +0100") Message-ID: <87my1aevro.fsf@devron.myhome.or.jp> MIME-Version: 1.0 List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Jean-Pierre =?iso-8859-1?Q?Andr=E9?= Cc: Eric Blake , Miklos Szeredi , fuse-devel@lists.sourceforge.net, Linux Kernel Mailing List , xfs@oss.sgi.com, Christoph Hellwig Jean-Pierre Andr=E9 writes: > Hi again, Hi, >> Yes. AFAIK, fuse of kernel part is passing FATTR_MTIME without >> FATTR_ATIME to userland (i.e. FUSE_SET_ATTR_ATIME and >> FUSE_SET_ATTR_MTIME in libfuse). >> >> I think it's good to implement if it's not design decision of ntfs-3g. >> >> [BTW, just my guess though, it would be good to use "if (vaild& >> ATTR_XXX)" style, not "switch()" to support various combinations of >> flags] >> = > > Might be better, ... or not. Setting both mtime > and atime is much simpler than setting each one > individually. So both methods will end up having > to process three different situations. Well, I don't care the implementation detail. However, the combination might not be only three. E.g. if fs was exported as network fs's backend, so many combinations are possible. So, specified known combination can be fragile. (e.g. ATTR_MTIME | ATTR_SIZE, etc, etc.) > 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? Thanks. -- = OGAWA Hirofumi _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs