Hey Linus, /* Summary */ Earlier this week we sent a few minor fixes for the multi-grained timestamp work in [1]. While we were polishing those up after Linus realized that there might be a nicer way to fix them we received a regression report in [2] that fine grained timestamps break gnulib tests and thus possibly other tools. The kernel will elide fine-grain timestamp updates when no one is actively querying for them to avoid performance impacts. So a sequence like write(f1) stat(f2) write(f2) stat(f2) write(f1) stat(f1) may result in timestamp f1 to be older than the final f2 timestamp even though f1 was last written too but the second write didn't update the timestamp. Such plotholes can lead to subtle bugs when programs compare timestamps. For example, the nap() function in [2] will estimate that it needs to wait one ns on a fine-grain timestamp enabled filesytem between subsequent calls to observe a timestamp change. But in general we don't update timestamps with more than one jiffie if we think that no one is actively querying for fine-grain timestamps to avoid performance impacts. While discussing various fixes the decision was to go back to the drawing board and ultimately to explore a solution that involves only exposing such fine-grained timestamps to nfs internally and never to userspace. As there are multiple solutions discussed the honest thing to do here is not to fix this up or disable it but to cleanly revert. The general infrastructure will probably come back but there is no reason to keep this code in mainline. The general changes to timestamp handling are valid and a good cleanup that will stay. The revert is fully bisectable. Link: [1]: https://lore.kernel.org/all/20230918-hirte-neuzugang-4c2324e7bae3@brauner Link: [2]: https://lore.kernel.org/all/bf0524debb976627693e12ad23690094e4514303.camel@xxxxxxxxxxxxxxxxxxxx /* Testing */ clang: Ubuntu clang version 15.0.7 gcc: (Ubuntu 12.2.0-3ubuntu1) 12.2.0 All patches are based on v6.5-rc1 and have been sitting in linux-next. No build failures or warnings were observed. xfstests pass without regressions. /* Conflicts */ At the time of creating this PR no merge conflicts were reported from linux-next and no merge conflicts showed up doing a test-merge with current mainline. The following changes since commit ce9ecca0238b140b88f43859b211c9fdfd8e5b70: Linux 6.6-rc2 (2023-09-17 14:40:24 -0700) are available in the Git repository at: git@xxxxxxxxxxxxxxxxxxx:pub/scm/linux/kernel/git/vfs/vfs tags/v6.6-rc3.vfs.ctime.revert for you to fetch changes up to 647aa768281f38cb1002edb3a1f673c3d66a8d81: Revert "fs: add infrastructure for multigrain timestamps" (2023-09-20 18:05:31 +0200) Please consider pulling these changes from the signed v6.6-rc3.vfs.ctime.revert tag. Thanks! Christian ---------------------------------------------------------------- v6.6-rc3.vfs.ctime.revert ---------------------------------------------------------------- Christian Brauner (5): Revert "tmpfs: add support for multigrain timestamps" Revert "xfs: switch to multigrain timestamps" Revert "ext4: switch to multigrain timestamps" Revert "btrfs: convert to multigrain timestamps" Revert "fs: add infrastructure for multigrain timestamps" fs/btrfs/file.c | 24 ++++++++++-- fs/btrfs/super.c | 5 +-- fs/ext4/super.c | 2 +- fs/inode.c | 82 ++--------------------------------------- fs/stat.c | 41 +-------------------- fs/xfs/libxfs/xfs_trans_inode.c | 6 +-- fs/xfs/xfs_iops.c | 6 +-- fs/xfs/xfs_super.c | 2 +- include/linux/fs.h | 46 +---------------------- mm/shmem.c | 2 +- 10 files changed, 38 insertions(+), 178 deletions(-)
