All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Allison <jra@samba.org>
To: Steve French <smfrench@gmail.com>
Cc: David Howells <dhowells@redhat.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: Mon, 28 Jun 2010 09:48:54 -0700	[thread overview]
Message-ID: <20100628164854.GA9979@samba1> (raw)
In-Reply-To: <AANLkTikkaRYyUfHILDCKYzXdLi9ORuQs05Rf9TScF_Tz@mail.gmail.com>

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.

Jeremy.

  reply	other threads:[~2010-06-28 16:48 UTC|newest]

Thread overview: 20+ 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
     [not found] ` <20100628162626.6026.26679.stgit-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2010-06-28 16:33   ` Steve French
2010-06-28 16:33     ` Steve French
2010-06-28 16:48     ` Jeremy Allison [this message]
2010-06-28 17:04       ` Steve French
2010-06-28 17:04         ` Steve French
     [not found]         ` <AANLkTilkfPkvyuQvN9zKrrY3DhJZ5iUfa5RXfErFwTiA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-28 17:14           ` Jeremy Allison
2010-06-28 17:14             ` Jeremy Allison
2010-06-28 19:21         ` Christoph Hellwig
2010-06-29 22:44       ` David Howells
     [not found]         ` <26197.1277851477-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-06-29 22:59           ` Jeremy Allison
2010-06-29 22:59             ` Jeremy Allison
2010-06-29 23:31             ` David Howells
2010-06-28 19:08 ` Andreas Dilger
     [not found] ` <19AAF9AA-2445-4C73-808B-4AD9C5C7E769-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org>
2010-06-28 19:38   ` David Howells
2010-06-28 19:38     ` David Howells
2010-06-28 19:41     ` Steve French
2010-06-28 19:41       ` Steve French
     [not found]       ` <AANLkTikhZn15GmOTe-fsM2IgxHFxtZIRBOb_4kPWSR4E-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-29 18:13         ` Andreas Dilger
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=20100628164854.GA9979@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.