| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20061005200726.GW22010@schatzie.adilger.int> Date: Thu, 5 Oct 2006 14:07:26 -0600 From: Andreas Dilger <adilger@...sterfs.com> To: Theodore Tso <tytso@....edu> Cc: Bj�rn JACKE <bjacke@...net.de>, ext3-users@...hat.com, linux-ext4@...r.kernel.org Subject: Re: creation time stamps for ext4 ? On Oct 05, 2006 12:55 -0400, Theodore Tso wrote: > > I've given this some thought for adding creation time as part of the nsec > > timestamp patch. That is more feasable if we move the nsec ctime into > > the main inode to double as the version field. > > Shoehorning an extra creation time field into the inode is relatively > easy, but it's also necessary to have system calls to get and set the > creation time. The stat structure doesn't have room for the creation > time, so that means a new version of the stat structure exported the > kernel, and a new version of the stat structure exported by glibc. For Lustre and NFSv4, an in-kernel interface is sufficient. I was thinking that as a preliminary userspace interface we can use getxattr with a standard name like user.crtime. Storing the crtime directly in the inode is more efficient than a separate EA, but it would also be compatible if Samba wanted to use real EAs to store this in the absence of large inodes. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists