On Wed, 2022-09-07 at 21:37 +1000, NeilBrown wrote: > On Wed, 07 Sep 2022, Jeff Layton wrote: > > I'm proposing to expose the inode change attribute via statx [1]. Document > > what this value means and what an observer can infer from it changing. > > > > Signed-off-by: Jeff Layton <jlayton@xxxxxxxxxx> > > > > [1]: https://lore.kernel.org/linux-nfs/20220826214703.134870-1-jlayton@xxxxxxxxxx/T/#t > > --- > > man2/statx.2 | 8 ++++++++ > > man7/inode.7 | 39 +++++++++++++++++++++++++++++++++++++++ > > 2 files changed, 47 insertions(+) > > > > v4: add paragraph pointing out the lack of atomicity wrt other changes > > > > I think these patches are racing with another change to add DIO > > alignment info to statx. I imagine this will go in after that, so this > > will probably need to be respun to account for contextual differences. > > > > What I'm mostly interested in here is getting the sematics and > > description of the i_version counter nailed down. > > > > diff --git a/man2/statx.2 b/man2/statx.2 > > index 0d1b4591f74c..d98d5148a442 100644 > > --- a/man2/statx.2 > > +++ b/man2/statx.2 > > @@ -62,6 +62,7 @@ struct statx { > > __u32 stx_dev_major; /* Major ID */ > > __u32 stx_dev_minor; /* Minor ID */ > > __u64 stx_mnt_id; /* Mount ID */ > > + __u64 stx_ino_version; /* Inode change attribute */ > > }; > > .EE > > .in > > @@ -247,6 +248,7 @@ STATX_BTIME Want stx_btime > > STATX_ALL The same as STATX_BASIC_STATS | STATX_BTIME. > > It is deprecated and should not be used. > > STATX_MNT_ID Want stx_mnt_id (since Linux 5.8) > > +STATX_INO_VERSION Want stx_ino_version (DRAFT) > > .TE > > .in > > .PP > > @@ -407,10 +409,16 @@ This is the same number reported by > > .BR name_to_handle_at (2) > > and corresponds to the number in the first field in one of the records in > > .IR /proc/self/mountinfo . > > +.TP > > +.I stx_ino_version > > +The inode version, also known as the inode change attribute. See > > +.BR inode (7) > > +for details. > > .PP > > For further information on the above fields, see > > .BR inode (7). > > .\" > > +.TP > > .SS File attributes > > The > > .I stx_attributes > > diff --git a/man7/inode.7 b/man7/inode.7 > > index 9b255a890720..8e83836594d8 100644 > > --- a/man7/inode.7 > > +++ b/man7/inode.7 > > @@ -184,6 +184,12 @@ Last status change timestamp (ctime) > > This is the file's last status change timestamp. > > It is changed by writing or by setting inode information > > (i.e., owner, group, link count, mode, etc.). > > +.TP > > +Inode version (i_version) > > +(not returned in the \fIstat\fP structure); \fIstatx.stx_ino_version\fP > > +.IP > > +This is the inode change counter. See the discussion of > > +\fBthe inode version counter\fP, below. > > .PP > > The timestamp fields report time measured with a zero point at the > > .IR Epoch , > > @@ -424,6 +430,39 @@ on a directory means that a file > > in that directory can be renamed or deleted only by the owner > > of the file, by the owner of the directory, and by a privileged > > process. > > +.SS The inode version counter > > +.PP > > +The > > +.I statx.stx_ino_version > > +field is the inode change counter. Any operation that would result in a > > +change to \fIstatx.stx_ctime\fP must result in an increase to this value. > > +The value must increase even in the case where the ctime change is not > > +evident due to coarse timestamp granularity. > > +.PP > > +An observer cannot infer anything from amount of increase about the > > +nature or magnitude of the change. If the returned value is different > > +from the last time it was checked, then something has made an explicit > > +data and/or metadata change to the inode. > > +.PP > > +The change to \fIstatx.stx_ino_version\fP is not atomic with respect to the > > +other changes in the inode. On a write, for instance, the i_version it usually > > +incremented before the data is copied into the pagecache. Therefore it is > > +possible to see a new i_version value while a read still shows the old data. > > Doesn't that make the value useless? > No, I don't think so. It's only really useful for comparing to an older sample anyway. If you do "statx; read; statx" and the value hasn't changed, then you know that things are stable. > Surely the change number must > change no sooner than the change itself is visible, otherwise stale data > could be cached indefinitely. > > If currently implementations behave this way, surely they are broken. It's certainly not ideal but we've never been able to offer truly atomic behavior here given that Linux is a general-purpose OS. The behavior is a little inconsistent too: The c/mtime update and i_version bump on directories (mostly) occur after the operation. c/mtime updates for files however are mostly driven by calls to file_update_time, which happens before data is copied to the pagecache. It's not clear to me why it's done this way. Maybe to ensure that the metadata is up to date in the event that a statx comes in? Improving this would be nice, but I don't see a way to do that without regressing performance. -- Jeff Layton <jlayton@xxxxxxxxxx>
