From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=209.85.221.53 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795020651; b=odH5ljknYWE6tcW/yXBO0GcDdbK5zt/p6rMTtYJKpriHR8uwx49u6kzSaav8qjEE7hFL DviC4n5BaIHhonZpOv+6cBCy52CKeYbtB0cx1zAkNq5OtQHSQvQP9nkt2Ghr01zEZHH52 A+5cfu9f8pelktGyG9sMAuu/2wOox95T5eBhi8hATMKOvrkQhH5bbANHw1qjLS4DN7LY5 8BSazEjjYj8MTOcAt3gFpwRs3X5ewbs9jqcd2SxOJkOCUEzgVEgbib/QQEVjB0A580Nyi kehbQ7cpUNwd44S535Nmc6vMQXl7IOuTz+CQN8jgr8JEUEhZYEkaK6kgy32koidQMzg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795020651; 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=m3pvNF133wcwSGy+HdLA8hjMu+z12FMemfmO2dtjbkM=; b=gp1/OIzo+7RlTXvLjPBqgbcVj895t5TAH1nam9iW+vC4Yjlk3FvLEWV4UzPRkAVbQ/cu l10xkTvOepueKVd6r4aAwg0xLapNThqoGksiYYZ1eGV77eINW5euvyQBznsgePH1eRE6l 8OOObKpR0/aWQUKJ9W9ri8OJX50XnoljmvTHeg4XFaiCHpXnsDVAMOD+SZiLta+6SGTbS 3lPDYk3JHyQWX9GufkmH9yDqlt2j9AuEjjHpT0A+jmHt9H3+9LzbiFk2JV7dbo3GGb24y E452UbdOZT2elaOXMnt0KThe/0B38Pwai34mNWl+bHneH9Xw6yF39dwoxS4JDR2em3g== 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=pAt6ghYd; arc=none smtp.remote-ip=209.85.221.53 Received: from mail-wr1-f53.google.com (mail-wr1-f53.google.com [209.85.221.53]) (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 45D4E60A2608 for ; Wed, 18 Nov 2026 16:50:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 45D4E60A2608 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) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20260707 header.b=pAt6ghYd Received: by mail-wr1-f53.google.com with SMTP id ffacd0b85a97d-490d59c3edaso848365f8f.1 for ; Wed, 18 Nov 2026 08:50:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20260707; t=1795020650; x=1795625450; darn=vger.kernel.org; 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=m3pvNF133wcwSGy+HdLA8hjMu+z12FMemfmO2dtjbkM=; b=pAt6ghYdJ/7/HTIaJO6x4Wuc0RCUjEjzeD/MJj4QrpUWOv7saFOFm6foATaUxUurqB jLBwoBDZMtIzTdKmn/s+HJmfNDwmN/jYWy2a8oG74Il8wPXklVF/ZALAxDgIuYdkd+D3 ceh/NpyqW0XTixDdf0q68XM66B36EaX3cfRpDmysDDCy+PuExDokiO/xVmOO5KkQ751V 8T9fpnnH4mSXT2zNUaHg8bPeCyqwwqKWzAz0XEK2rh3bUBTZZx6PKMIrdK1DwOxDdF6S Xc4S+6zeDuayTBdb5OEXpV+Fk9gb/KN6tk4sQGu5caOPWrDhh17g11G2ZrDpE+FrCkaX S8eA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1795020650; x=1795625450; 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=m3pvNF133wcwSGy+HdLA8hjMu+z12FMemfmO2dtjbkM=; b=ZboN+ZhB66GvgBflIYpds629Hf/gwdMpCNY33ZysMPv1wtCAwFW5gZYuGB+87WIgXc qEBqRW6ms63WrHQC+tt2peihdGKbvTa1KYC5pYH42dwbBHUlhBfYYnR7VWkSqmEyUVvp 9iDEjOimMv7VtLRcCSj0JB27RfJnALzht84qZABwzZawbuHUCvBPFCGQtpSHN2xbdyCL ixOs9B+kYLt8Q9Nl/vhlLzm+LkleRPIChnPr/IG6QdXLPDyXYkU3twCKHN1p+cAcgpY5 XGGbl0untWHdg/lY5SVHuZsAWqBMA+kBWBErWBbyTtKTOKgxE3qRs5YBPZ/v3067fP+V HYJQ== X-Forwarded-Encrypted: i=1; AL+hErEtQWRi+atbmV1YHrnX8KZObbH8TjFp0xIwbaj4Ao0Fz1k7YfP+m6GBDE8cLMmNYv3Eubef+j8PwNU=@vger.kernel.org X-Gm-Message-State: APuU4Z9gEfiG8zkZcjJ9whxM3NBrude42hrwltwyJiBJN63AF3SbI7Fp cFGGmnvke5LohbkAU3JdlLTAtit5M8Jm1sVSqgyIIgCOcuj9IfQjUmQm X-Gm-Gg: AZFdTZcWPviDq2jks1/+kgbbY7J7gNZN5Cjhg9quQzFxr/DWubw0qn3dcyPDWUiUq4M I/uXYyWtSOkEdNydKajoWN7gFGtdwAVWTkoqiWWXnBCYmtVg6QtC9ZkpJvvmDIpz63rmBnQGJzH 69Cpfe/957SsBxsi8bWMakN67pZ2n4HNrlMSJ/OchhwP/X9qq3AlVd6tRiIE04uKpTrCNy97xUA KpN3idnsvrQDY74HeRSmHbBhXJs/BmmiKs1JZdOmdpu/Eu4hzNI7AZ7z6rIBTJdFhOcxmx9z/dh mfZYg/bCR8hT/9hk6YFk/jDftbiFV5e36meWLRczukXxPFAca0JvolVmxVlxs/VtTMNI6coXCs4 1wqE4XyEr2xIwZuvwe4xnfR15F7ketdNC42OKVB2Gw3rquYgKBSEywNoXGV24P3zsOSNzRAYBc0 Dq/JCETEoEo2uHgb7ZexnTd7/+FduClKotn2jO+3qW55iejFzAxCFo5bIneSwEqzal/NbalmNHX 1bEaEEz5Cc1od3NqF6jl/yQ2+yOztMUcZxyonoKRGh13Z4cxsktCcVhA3MXnT8JIR6aEhGvjonV CTA7hxHjWyrxa/a0tMC55cRDCGw= X-Received: by 2002:a05:6000:29d6:b0:48c:585b:8825 with SMTP id ffacd0b85a97d-4a8e60ff7eamr118137f8f.18.1795020649313; Wed, 18 Nov 2026 08:50:49 -0800 (PST) Received: from localhost ([2001:b07:5d26:7a6a:de3b:51f3:e461:c0df]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-4a650d2ecd0sm6451582f8f.8.2026.11.18.08.50.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 Nov 2026 08:50:48 -0800 (PST) X-Mailing-List: linux-api@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list Mime-Version: 1.0 Content-Type: multipart/signed; boundary=e68d7a3c08e03032b674b625d495d35f9a655e5ba7e0e8c8006911574197; micalg=pgp-sha512; protocol="application/pgp-signature" Date: Wed, 18 Nov 2026 17:50:39 +0100 Message-Id: Cc: "David Sterba" , "Namjae Jeon" , "Sungjong Seo" , "Alexander Viro" , "Christian Brauner" , "Trond Myklebust" , "Anna Schumaker" , "Chuck Lever" , "Jeff Layton" , "Konstantin Komarov" , "Paulo Alcantara" , "Chris Mason" , "Yuezhang Mo" , "Jan Kara" , "NeilBrown" , "Olga Kornievskaia" , "Dai Ngo" , "Tom Talpey" , "Ronnie Sahlberg" , "Shyam Prasad N" , "Bharath SM" , "Sergey Senozhatsky" , "ChenXiaoSong" , "Darrick J . Wong" , "Sean Smith" , "Andrey Albershteyn" , "Pedro Falcato" , "Amir Goldstein" , , , , , , , , Subject: Re: [RFC PATCH v4 00/10] add provenance time (ptime) From: "koraynilay" To: =?utf-8?q?Pali_Roh=C3=A1r?= , "koraynilay" X-Mailer: aerc 0.22.0-0-gc2f86b7abde3 References: <20261115180343.576773-1-koray.fra@gmail.com> <20261118142613.be3r3s6kobkkxnz4@pali> <20261118151605.lqtn5fz423kuswk5@pali> In-Reply-To: <20261118151605.lqtn5fz423kuswk5@pali> --e68d7a3c08e03032b674b625d495d35f9a655e5ba7e0e8c8006911574197 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 On Wed Nov 18, 2026 at 4:16 PM CET, Pali Roh=C3=A1r wrote: > On Wednesday 18 November 2026 15:58:02 koraynilay wrote: >> On Wed Nov 18, 2026 at 3:26 PM CET, Pali Roh=C3=A1r wrote: >> > Hello, >> > >> > I have just one issue with the userspace API. It does not allow me to >> > figure out what is the source of statx btime field. If it is fs ptime = or >> > fs btime because this RFC implementation is mixing both fs ptime and >> > fs btime into the statx btime field. >> > >> > I have feeling that this is quite a mess in API and I would like to se= e >> > a clear distinguish between btime and ptime in the API, like there is = a >> > difference in the fs storage. >> > >> > If the btime is used for forensic analysis then somehow I would expect >> > that the statx would not report / not fill changeable ptime value into >> > the statx btime. >>=20 >> Hi, for native linux filesystems it will report ptime as PTIME and btime >> as BTIME (also semnatically). > > That is fine. > >> for the windows-like ones that only have >> ptime (semantically) I think it's reasonable to not expect btime to be >> immutable, since they are meant to be used with other OSs who lack btime >> semantics. > > The problem is here that the RFC statx API does not provide this > information that the fs lacks btime semantics and instead it fills > non-immutable ptime value there. > > I'm pointing only about this inconsistency. > >> > It would be really helpful if the statx API on inode can differ betwee= n: >> > >> > 1. btime is present and its value is ..., ptime is not supported >> > 2. btime is not supported, ptime is set to value ... >> > 3. btime is present and its value is ..., ptime is set to value ... >> > 4. both btime and ptime are not supported >> > >> > This should cover all cases of different filesystems and also allows >> > userspace to do proper backup of both ptime and btime fields (if it wa= nt >> > to do forensic analysis or anything else). >>=20 >> These should already all be covered by STATX_BTIME/PTIME and their >> fields in struct statx, the only problems are windows-like filesystems, >> which IMO shuold be handled as mentioned above. > > Exactly, I pointed out about these problems. I somehow expect that the > new API would be generic and uniform across filesystem. IMHO it does not > matter if the filesystem is windows-like or not (there are also FreeBSD > fs and also others which allows to modify that time). So better > description is fs belongs to category 2. from my above description. Ah yes, I used windows-like to mean "only have ptime semantics", so same as your category 2. >> Of course, as in the other discussion, I'm open to changing ptime >> NTFS/exFAT/... support to remove btime altogether and only use ptime for >> their own crtime if that's what wanted (I'm fairly impartial on this >> specific issue). > > I'm giving some ideas how to possible handle this situation: > > 1. do not fill btime it at all when it is not available (remove btime > altogether - the case like you wrote above) This would be the most semantically correct option, but would break at least 1 script/program/use case. > 2. when userspace ask both ptime and btime, then do not fill btime > (remove btime altogether - but only for that new case) This probably is the best compromise. > 3. fill btime with ptime value, but add a new output flag indicating that > the btime is not present at all and instead kernel filled ptime value > into the statx btime field I don't really like this, it adds complexity and uses memory/1 flag big for a single specific field, IMO it's not worth it. > 4. let statx btime as currently is, and add two new statx fields: > immutable_btime and ptime. immutable_btime would be filled only if the > fs supports real btime (so not for ntfs/extfat crtime) and ptime would > be what is currently in RFC I think this is also too complex. > Ideas 2. 3. and 4. should be fully backward compatible as it would > affect statx output only when called with new flags. Then 2. is probably the best way to go forward (maybe I'll include it in some way in v5), but I think we should let each filesystem maintainer decide if they think their users want to have statx report their own crtime as btime, ptime or both (native linux ones would of course report btime as btime and ptime as ptime). Thanks, koraynilay >> Thanks, >> koraynilay >>=20 >> > >> > Pali --e68d7a3c08e03032b674b625d495d35f9a655e5ba7e0e8c8006911574197 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRJ2XvJtXGwULYEerQ0bnTtJTDoOAUCav3XXwAKCRA0bnTtJTDo OHCeAQCEIeCKM23PngeIMoBXCQU9k+fpxVE5Iim2Z6kczs7U7QD/QrQdNXwKde9D 5NVqKpZ3hIlgyN/x854bwe3ySGv/rQc= =h4y9 -----END PGP SIGNATURE----- --e68d7a3c08e03032b674b625d495d35f9a655e5ba7e0e8c8006911574197--