All of lore.kernel.org
 help / color / mirror / Atom feed
From: "koraynilay" <koray.fra@gmail.com>
To: "Jan Kara" <jack@suse.cz>, "koraynilay" <koray.fra@gmail.com>
Cc: "David Sterba" <dsterba@suse.com>,
	"Alexander Viro" <viro@zeniv.linux.org.uk>,
	"Christian Brauner" <brauner@kernel.org>,
	"Chris Mason" <mason@kernel.org>,
	"Darrick J . Wong" <djwong@kernel.org>,
	"Sean Smith" <defendthedisabled@gmail.com>,
	"Andrey Albershteyn" <aalbersh@kernel.org>,
	<linux-btrfs@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/2] add provenance time (ptime)
Date: Wed, 04 Nov 2026 12:37:22 +0100	[thread overview]
Message-ID: <DMMEA3RCJIIR.3M3VFS656X8B7@gmail.com> (raw)
In-Reply-To: <unzslqbr7karhkgfxrcmjwgtps3byokmsqecyouqlc7aa6cszv@pgup6q2nxwt6>

[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]

On Wed Nov 4, 2026 at 12:33 PM CET, Jan Kara wrote:
> On Tue 03-11-26 15:26:20, koraynilay wrote:
>> On Tue Nov 3, 2026 at 2:25 PM CET, Jan Kara wrote:
>> > On Tue 27-10-26 23:05:30, koraynilay wrote:
>> >> This is an initial implementation of a new timestamp to indicate the
>> >> time when a file/directory was initially created.
>> >> 
>> >> This patch series takes inspiration from the one by Sean Smith
>> >> <defendthedisabled@gmail.com> [1], but using
>> >> file_setattr()/file_getattr() as suggested by Darrick J. Wong
>> >> <djwong@kernel.org> in [2].
>> >> 
>> >> The semantics of this new timestamp should be at least these:
>> >> - it should be the same as btime on a newly created file
>> >> - it's user-settable, so it can be preserved for backups, filesystem
>> >>   conversions, archives and any similar operation
>> >> - it should be preserved every time mtime gets preserved
>> >> 
>> >> and the correspondence with the other timestamps is as follows:
>> >> 
>> >> ctime <-> btime
>> >> mtime <-> ptime
>> >
>> > One thing I miss in this series is an explanation what this new timestamp is
>> > good for. Because frankly, I don't miss such timestamp as a Linux user :).
>> >
>> > 								Honza
>> 
>> Hello, my concrete use-cases are backups and filesystem conversions.
>> 
>> For backups, my setup is btrfs and using btrbk (so btrfs send to my nas
>> with ssh) and the only missing thing from the backup is the timestamp of
>> file creation (which I'm currently working around using xattrs).
>> 
>> The situation that prompted me to finally start working on this RFC
>> PATCH was when I wanted to merge 2 btrfs FSs and the only way of doing
>> that (AFAIK at least) is using cp/rsync, which can't set the creation
>> time since btime is immutable. The workaround I used was the same as
>> with backups, so with xattrs, but noticed that some files (symlinks)
>> wouldn't accept xattrs, so I looked into it and found out xattrs are
>> only for regular files/dirs.
>> 
>> (also see https://lore.kernel.org/DMGS4KQLY24Q.14MUTR6U93GIC@gmail.com/)
>
> Ah, OK, I think I finally understand why do you want this. Thanks for
> explanation!
>
> 								Honza

Nice, thank you!

Best,
koraynilay

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-11-04 11:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 22:05 [RFC PATCH 0/2] add provenance time (ptime) koraynilay
2026-10-27 22:05 ` [RFC PATCH 1/2] vfs: " koraynilay
2026-10-27 22:05 ` [RFC PATCH 2/2] btrfs: " koraynilay
2026-11-03 13:25 ` [RFC PATCH 0/2] " Jan Kara
2026-11-03 14:26   ` koraynilay
2026-11-04 11:33     ` Jan Kara
2026-11-04 11:37       ` koraynilay [this message]

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=DMMEA3RCJIIR.3M3VFS656X8B7@gmail.com \
    --to=koray.fra@gmail.com \
    --cc=aalbersh@kernel.org \
    --cc=brauner@kernel.org \
    --cc=defendthedisabled@gmail.com \
    --cc=djwong@kernel.org \
    --cc=dsterba@suse.com \
    --cc=jack@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@kernel.org \
    --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.