Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=209.85.221.43 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793726518; b=xHZEZVlBQjVbu2MjaQjzhAdIQTnOgsvR7vk0m7K1lTB2N2XEAUaaF36gb/GBgb0C53/U WIQrA6UaXBqy/2cpz+YoF3utN1ggayn/BKMjmYZb8/YW74ILfPM8AbK1IUHu9pia0T4eu P0KjyrauLaXcUPCvrku2wTk8CLIgCxNVMCtJcFZZ9GEy1VTnTpnz6zpIjnVwCygLjABBS 200lSkjsyAiqwxQe0GrvxL+Dd0+pjPQGwf9FGFSQBFUxPsVZRF7ZKpnQc7B4An/NNoWFq Tr3N0PSczUuZOLc3b/NRh2wQJbU86FADI32iJ96rLsJl21/Fyv3GSh3d77MS7QL/f7w== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793726518; h=DMARC-Filter:Received:DKIM-Signature:X-Google-DKIM-Signature: X-Forwarded-Encrypted:X-Gm-Message-State:X-Gm-Gg:X-Received:Received: Mime-Version:Content-Type:Date:Message-Id:Cc:Subject:From:To:X-Mailer: References:In-Reply-To; bh=AD4L42H0HNVoYlglqMFr39a2BJYBFr7pQM1pceNP/MA=; b=ikieuurzQaU0+OKZ+TASjUtsdpnddStDrXpICtPhoiqIAQ6cZYJBI5fMBzVw6CIUwQA9 0vAhIW5mIALuQ2wfUt+lvR6zHBxNBdPNjL9DA7RqcIep/29Y1F7g7sXJcQ9dP2DzgiPOr xadBtt6UiAsi8y3GvdVKuus6ijCedjJST/G+hQ8zGToBS4LoP2Kc1K/6kCqbzWwyMBu8V oKDhKQvBfYP6aRLlBiaHHUs/ehtgXx2Jf8M3QfHcWnrt/72g4WdqWMxc+phM556pX2wCH 1ID2jC47B2nN3Y2QbAchXn2KE/X9A0xjFQGHMo5hGq+aMUkZnurIyqQLq/2d/IeM3Vw== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20260707 header.b=MBhNH4lb; arc=none smtp.remote-ip=209.85.221.43 Received: from mail-wr1-f43.google.com (mail-wr1-f43.google.com [209.85.221.43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A3DE2606A32C for ; Tue, 3 Nov 2026 17:21:57 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org A3DE2606A32C Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20260707 header.b=MBhNH4lb Received: by mail-wr1-f43.google.com with SMTP id ffacd0b85a97d-48c4be28b82so4615487f8f.2 for ; Tue, 03 Nov 2026 09:21:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20260707; t=1793726516; x=1794331316; darn=lists.linux.dev; h=in-reply-to:references:to:from:subject:cc:message-id:date :content-type:mime-version:from:to:cc:subject:date:message-id :reply-to:content-type; bh=AD4L42H0HNVoYlglqMFr39a2BJYBFr7pQM1pceNP/MA=; b=MBhNH4lbjHVjov9tsn+tt2t2re+N4KTTSAWHXb0AUqfhiV25n27MdDXgj9HwLdnOgf pp3+hI9h7YkZ6/x4LFzfp7+DvFe/3FfAWDloKKu/oMfnJbqItkoAqKX51a6hQcBmAj62 jcEGfyGZr6aFTpOPZHrhlpVRaRd1CVFCkVRwp4mueoAViH8+kzz9h9KB4wwsp+YvCg5O fl3Sdli1aHBR9gSm0ZL7RrD/+WudmHEedvxeraoXPOfoxIttmmRlOaRUMcG/kucTQLVo ajWOURbn24/F+4nXOA1dMSEoohUc4rZkp7ID5Kb6f8q+3YBz2RuAhqjkbScUL2/13Dk+ chvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1793726516; x=1794331316; h=in-reply-to:references:to:from:subject:cc:message-id:date :content-type:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=AD4L42H0HNVoYlglqMFr39a2BJYBFr7pQM1pceNP/MA=; b=c8hZLrNnJHKvVTCjWjKQBw20oy2tJPSmBayeo7TZn/1yS4tJ/GlyhaXM5IEhR7M8rj 9+4qlKEF/uFHAXcmFhmeU9x0GCHLddyfirOGeAimgTH1qUD8tXh/hTwQrqIy9naUIrMl wVhoMzlF/uDSrjIfLk6XFbC5O9GDT8/ILztY/s5XwGoWcS2cOEEfT7PRlGBB5BcDfj44 4cXfGqBZKz8HPHYtxLesBMzG2mhs+SUh3cEvU19UVdumNcSdb8s839o8JvNQHNczAqTY Jbcd+s5QRae9GGQfX/b+jGOHPmonIhM7deXbhVgn8CwMmckx/50mSJza9ZfgnqcUIg+E VOQw== X-Forwarded-Encrypted: i=1; AKwUvBwoH1UkYJYh4pgZJeTqDkjlHWiHt0Uk8Men/oHwPViyjItE+gV5jhPsZbFcfM0ACMpjSVYS4Q==@lists.linux.dev X-Gm-Message-State: APuU4Z8BzUVpX9Yu0FBe+fdaJ+zk+zVfMDFMDDvYw31PDcZKX+G6OkbI kDUffIPtJMLcIWbpwIneuYVSj28nosZFyQFznxxZ5VdYjIXR68S3d1yn X-Gm-Gg: AYBFou3NiDO4iD9dZRJjWeKKj5bTwmdNxMOLVo3pg3bbyAA/KyfM50etvaxjmjBeIKB dFpNy1N3b5z+wIwqEB08m2UPAZJrfPZ4dCtwbq5s8uXyXMGUcH4scVkHBUZQsYz3pzarMorwewK ts0POENJ44i1Igr5NjoGb/t7Y9CVXCeqgKLqhtZ4tPwD+PMEjZbIB51TMD4nR4GMkNNYEPpznFy FTrfG8mH7DHR1WrPajbFM6+JN/RvQRNm6JjGJn/YW7uGO30htYSa+6e9edico4tLHH7fUYalr0d gagpR+GnQ4zAasZwHCbxOd5Dc5q7bX0AamWeOj2BkXcKxGQh46lzNBrB1rTW5Bav13nvYUxbVtP fwB4BYBuqCAfDM83UJtB2UCRLKDBVl/HFdKW2FsV0YVQ5kCjGkT7x62bwIrw1eo7DNNvB3kTu9y ZlYVpdZFHEGFpoyNlC7fQeMfas/gymWHP07JVOz32g4pgzTxyw6UHSAgu9Fn7b4x8NIbfAH+oss krx41LrgZuqDhjhpwrqdCgHNCR4kcZSDGpGekYTzmw+alTdG71sNIstF6n+Q8cXq8u8GHS/8inJ wzBKjpDUIwq7dveGOBiIiOFU X-Received: by 2002:a05:600c:3b0e:b0:4a7:7d22:c50c with SMTP id 5b1f17b1804b1-4ac150b2243mr345177055e9.2.1793726515970; Tue, 03 Nov 2026 09:21:55 -0800 (PST) Received: from localhost ([151.60.201.12]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4ac0a66caefsm287061365e9.5.2026.11.03.09.21.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 Nov 2026 09:21:55 -0800 (PST) X-Mailing-List: exfat@lists.linux.dev List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list Mime-Version: 1.0 Content-Type: multipart/signed; boundary=1ae0fec9eeabe43856471b243f1ece3413edf7686407593b3575066613d8; micalg=pgp-sha512; protocol="application/pgp-signature" Date: Tue, 03 Nov 2026 18:21:53 +0100 Message-Id: Cc: "David Sterba" , "Alexander Viro" , "Christian Brauner" , "Namjae Jeon" , "Sungjong Seo" , "Konstantin Komarov" , "Chris Mason" , "Jan Kara" , "Yuezhang Mo" , "Chuck Lever" , "Darrick J . Wong" , "Sean Smith" , "Andrey Albershteyn" , "Pedro Falcato" , =?utf-8?q?Pali_Roh=C3=A1r?= , , , , , , Subject: Re: [RFC PATCH v3 0/5] add provenance time (ptime) From: "koraynilay" To: "Amir Goldstein" , "koraynilay" X-Mailer: aerc 0.22.0-0-gc2f86b7abde3 References: <20261101015551.786044-1-koray.fra@gmail.com> In-Reply-To: --1ae0fec9eeabe43856471b243f1ece3413edf7686407593b3575066613d8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 On Tue Nov 3, 2026 at 4:12 PM CET, Amir Goldstein wrote: > On Tue, Nov 3, 2026 at 12:25=E2=80=AFPM koraynilay = wrote: >> >> On Mon Nov 2, 2026 at 3:54 PM CET, Amir Goldstein wrote: >> > On Sun, Nov 1, 2026 at 2:57=E2=80=AFAM 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 >> >> [1], but using >> >> file_setattr()/file_getattr() as suggested by Darrick J. Wong >> >> 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 >> >> >> >> Examples: >> >> 1) a .zsh_history file created in 2019, then after a few years the us= er >> >> decides to switch to another filesystem, copying the .zsh_history = to >> >> the new home, in that case btime would have the timestamp of the c= opy >> >> and ptime would have the 2019 timestamp (just like mtime would hav= e >> >> been preserved) >> >> 2) a symlink created in 2020 from the home directory to a /path going >> >> through the same process as the .zsh_history, in this case it woul= d >> >> also make sense to sync the ptime to the 2020 timestamp instead of >> >> keeping only the btime (so the inode creation time). >> >> >> >> The proof-of-concept code (for testing) for stat(1) and cp(1) is >> >> available at https://github.com/koraynilay/coreutils (master branch) >> >> (Note: these coreutils code changes are a prototype and won't be >> >> submitted upstream as-is, but they work as expected in simple stat an= d >> >> cp -a/--preserve=3Dptime tests) >> >> >> >> Lastly, the name "provenance" and "ptime" are not final, I personally >> >> don't have a strong opinion on any name, but while testing with stat(= 1) >> >> I noticed that "Provenance" is definitely too long for the normal >> >> output, so another option which would fit well is "Origin time", >> >> abbreviated as "ntime" (OrigiN time) and not as "otime", as that woul= d >> >> conflict with btrfs' internal naming and create confusion. >> > >> > FWIW, I agree that given the existing uses of btime and crtime in the >> > kernel and various XXXprogs, using 'ptime' for kernel code is probably >> > the lesser evil. >> >> What do you think about the origiN time (ntime) (Origin: in stat)? >> It would also coincidentally be alphabetically (ntime <-> mtime, n -> m) >> the same as btime <-> ctime (b -> c) ahah. >> > > Honestly I don't know. > My new idea is don't publish it in statx() at all. Well I was more talking about the actual variable names in all patches ahah. Thanks, koraynilay > Thanks, > Amir. --1ae0fec9eeabe43856471b243f1ece3413edf7686407593b3575066613d8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRJ2XvJtXGwULYEerQ0bnTtJTDoOAUCauoYMQAKCRA0bnTtJTDo OI2UAQDfLMxbWJxZCtj5g/a2TQHWFv3yLHmv7IEjclN8pYY5IgD/VFtdYZ3g+FW5 oxEEhXF7xBfTTV5O+6Ag8QIL/lM51wc= =XiPH -----END PGP SIGNATURE----- --1ae0fec9eeabe43856471b243f1ece3413edf7686407593b3575066613d8--