cifs: define inode-level cache object and register them
in [Kernel]
|
Prev: [PATCH] usb gadget, serial: Add a serial number field to the usb descriptor.
Next: [PATCH for stable] tracing: Consolidate protection of reader access to the ring buffer
From: Steve French on 25 Jun 2010 19:10 On Fri, Jun 25, 2010 at 5:26 PM, Jeff Layton <jlayton(a)samba.org> wrote: > > On Fri, 25 Jun 2010 22:46:38 +0100 > David Howells <dhowells(a)redhat.com> wrote: > > > Jeff Layton <jlayton(a)samba.org> wrote: > > > > > Looks like it mostly uses the ctime. IMO, the mtime would be a better > > > choice since it changes less frequently, but I don't guess that it > > > matters very much. > > > > I'd've thought mtime changes more frequently since that's altered when data is > > written. �ctime is changed when attributes are changed. > > > > IIUC, updating mtime for a write is also an attribute change, and that > affects ctime. According to the stat(2) manpage: > > � � � The field st_ctime is changed by writing or by setting �inode �informa- > � � � tion (i.e., owner, group, link count, mode, etc.). > > > Note that Ext4 appears to have a file creation time field in its inode > > (struct ext4_inode::i_crtime[_extra]). �Can Samba be made to use that? > > > > Is it exposed to userspace in any (standard) way? It would be handy to > have that. While we're wishing...it might also be nice to have a > standard way to get at the i_generation from userspace too. > Yes - I have talked with MingMing and Aneesh about those (NFS may someday be able to use those too).� An obstacle in the past had been that samba server stores its own fake creation time in an ndr encoded xattr which complicates things. MingMing/Annesh - Xattr or other way to get at birth time? -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |