From: Jeremy Allison <jra@samba.org>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
Boris Protopopov <boris.v.protopopov@gmail.com>,
samba-technical <samba-technical@lists.samba.org>,
David Howells <dhowells@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] Add support for setting owner info, dos attributes, and create time
Date: Mon, 13 Jan 2020 12:36:13 -0800 [thread overview]
Message-ID: <20200113203613.GA111855@jra4> (raw)
In-Reply-To: <780DD595-1F92-4C34-A323-BB32748E5D07@dilger.ca>
On Mon, Jan 13, 2020 at 01:26:39PM -0700, Andreas Dilger via samba-technical wrote:
> On Jan 9, 2020, at 12:10 PM, Steve French <smfrench@gmail.com> wrote:
> >
> > One loosely related question ...
> >
> > Your patch adds the ability to set creation time (birth time) which
> > can be useful for backup/restore cases, but doesn't address the other
> > hole in Linux (the inability to restore a files ctime).
> >
> > In Linux the ability to set timestamps seems quite limited (utimes
> > only allows setting mtime and atime).
>
> The whole point of not being able to change ctime and btime as a regular
> user is so that it is possible to determine when a file was actually
> created on the filesystem and last modified. That is often useful for
> debugging or forensics reasons.
>
> I think if this is something that SMB/CIFS wants to do, it should save
> these attributes into an xattr of its own (e.g. user.dos or whatever),
> rather than using the ctime and btime(crtime) fields in the filesystem.
FYI, we (Samba) already do this for create time to store/fetch it
on systems and filesystems that don't store a create time. It's
easy to add extra info here.
next prev parent reply other threads:[~2020-01-13 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 16:52 [PATCH] Add support for setting owner info, dos attributes, and create time Boris Protopopov
2020-01-09 19:10 ` Steve French
2020-01-13 20:17 ` Boris Protopopov
2020-01-13 20:26 ` Andreas Dilger
2020-01-13 20:36 ` Jeremy Allison [this message]
2020-01-13 22:17 ` Boris Protopopov
2020-01-15 21:18 ` Steve French
2020-01-16 21:20 ` Boris Protopopov
2020-01-17 2:25 ` Steve French
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=20200113203613.GA111855@jra4 \
--to=jra@samba.org \
--cc=adilger@dilger.ca \
--cc=boris.v.protopopov@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).