From: Jeremy Allison <jra@samba.org>
To: David Howells <dhowells@redhat.com>
Cc: Jeremy Allison <jra@samba.org>, Steve French <smfrench@gmail.com>,
viro@zeniv.linux.org.uk, jlayton@redhat.com, mcao@us.ibm.com,
aneesh.kumar@linux.vnet.ibm.com, linux-cifs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
samba-technical@lists.samba.org, sjayaraman@suse.de,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] Ext4: Make file creation time, i_version and i_generation available by xattrs
Date: Tue, 29 Jun 2010 15:59:44 -0700 [thread overview]
Message-ID: <20100629225944.GA22924@samba1> (raw)
In-Reply-To: <26197.1277851477@redhat.com>
On Tue, Jun 29, 2010 at 11:44:37PM +0100, David Howells wrote:
> Jeremy Allison <jra@samba.org> wrote:
>
> > We already have code in Samba to detect "birthtime"
> > (st_btime) as a returned member of a stat struct.
>
> Is it, though?
>
> Googling for st_btime suggests it could also be taken as the time last
> archived. That may just be a NetWareism though.
It's a *BSD'ism.
http://www.daemon-systems.org/man/fstat.2.html
#if defined(_NETBSD_SOURCE)
struct timespec st_birthtimespec; /* time of inode creation */
#else
time_t st_birthtime; /* time of inode creation */
long st_birthtimensec; /* nsec of inode creation */
#endif
http://www.unix.com/man-page/FreeBSD/2/stat/
st_birthtime Time when the inode was created.
Of course, for Samba's use we also have to be
able to *write* to st_birthtime as Windows clients
can change this. But that's what the EA is for
(and I'm happy with a system that can only read
st_birthtime, not write it).
Jeremy.
next prev parent reply other threads:[~2010-06-29 22:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 16:26 [PATCH] Ext4: Make file creation time, i_version and i_generation available by xattrs David Howells
2010-06-28 16:33 ` Steve French
2010-06-28 16:48 ` Jeremy Allison
2010-06-28 17:04 ` Steve French
2010-06-28 17:14 ` Jeremy Allison
2010-06-28 19:21 ` Christoph Hellwig
2010-06-29 22:44 ` David Howells
2010-06-29 22:59 ` Jeremy Allison [this message]
2010-06-29 23:31 ` David Howells
2010-06-28 19:08 ` Andreas Dilger
2010-06-28 19:38 ` David Howells
2010-06-28 19:41 ` Steve French
2010-06-29 18:13 ` Andreas Dilger
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=20100629225944.GA22924@samba1 \
--to=jra@samba.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcao@us.ibm.com \
--cc=samba-technical@lists.samba.org \
--cc=sjayaraman@suse.de \
--cc=smfrench@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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