From: Trond Myklebust Subject: Re: [PATCH 02/18] xstat: Add a pair of system calls to make extended file stats available [ver #6] Date: Sat, 31 Jul 2010 15:03:52 -0400 Message-ID: <1280603032.3125.24.camel@heimdal.trondhjem.org> References: <20100715021712.5544.44845.stgit@warthog.procyon.org.uk> <30448.1279800887@redhat.com> <20100722162712.GB10352@jeremy-laptop> <1279817930.3621.14.camel@heimdal.trondhjem.org> <20100722180204.GA32008@samba1> <1279825160.3621.71.camel@heimdal.trondhjem.org> <4C5311F4.2050100@psu.edu> <1280513506.12852.22.camel@heimdal.trondhjem.org> <09B770A6-48DB-4296-B6C2-BF46D4DC7E57@dilger.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Phil Pishioneri , Volker.Lendecke-PS7XAnAlDA+VvDNblw4Uiw@public.gmane.org, Jeremy Allison , Linus Torvalds , David Howells , Jan Engelhardt , linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andreas Dilger Return-path: In-Reply-To: <09B770A6-48DB-4296-B6C2-BF46D4DC7E57-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org> Sender: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-ext4.vger.kernel.org On Sat, 2010-07-31 at 12:41 -0600, Andreas Dilger wrote: > On 2010-07-30, at 12:11, Trond Myklebust wrote: > > Your Mac has a perfectly functional CIFS client, as do your Linux boxes. > > They both interoperate just fine with Samba, and would presumably > > continue to do so if someone were to decide to reuse the ctime field on > > your Samba box as storage for a create time. > > CIFS doesn't support symlinks (they just appear as the referenced file), so I've had applications that scan the filesystem recurse indefinitely due to symlinked directories on a CIFS share appearing as hard-linked directories on the client. This doesn't happen when the filesystem is accessed via NFS. Sigh... So please explain how it would be useful to export that particular filesystem through _both_ CIFS and NFS? My point was that in most circumstances you want to export either through CIFS or through NFS, but very rarely both. I also made the point that converting ctime into a creation time would break NFS, but it would be a limited breakage, mainly affecting the client's ability to detect ACL changes, and possibly causing the inode to get temporarily updated with stale attribute information on occasion due to out-of-order RPC replies. Trond