[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTilkfPkvyuQvN9zKrrY3DhJZ5iUfa5RXfErFwTiA@mail.gmail.com>
Date: Mon, 28 Jun 2010 12:04:09 -0500
From: Steve French <smfrench@...il.com>
To: Jeremy Allison <jra@...ba.org>
Cc: David Howells <dhowells@...hat.com>, viro@...iv.linux.org.uk,
jlayton@...hat.com, mcao@...ibm.com,
aneesh.kumar@...ux.vnet.ibm.com, linux-cifs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
samba-technical@...ts.samba.org, sjayaraman@...e.de,
linux-ext4@...r.kernel.org
Subject: Re: [PATCH] Ext4: Make file creation time, i_version and i_generation
available by xattrs
On Mon, Jun 28, 2010 at 11:48 AM, Jeremy Allison <jra@...ba.org> wrote:
> On Mon, Jun 28, 2010 at 11:33:10AM -0500, Steve French wrote:
>>
>> It would be easy enough to do something similar for crtime for cifs
>> (it may also be possible to do something similar to
>> i_generation and i_version at least for smb2 but haven't
>> experimented to see which servers could return something
>> similar to version and generation). I did have a request for
>> someone doing a backup application over cifs to return creation
>> time so at least this would make sense.
>
> We already have code in Samba to detect "birthtime"
> (st_btime) as a returned member of a stat struct.
>
> This already works on many other platforms, so I'd
> rather just have Linux stat fixed to work with
> btime.
That sounds better but it hits the fs, vfs and libc
and seems like libc is near impossible to get changes into.
Seems like in the short term adding xattrs is harmless, and
doesn't hurt in the longrun
--
Thanks,
Steve
--
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