v2: - drop gfs2 patch as it involved (hidden) quota inode - clarify patch descriptions to satisfy checkpatch.pl While working on a patch series to change how we handle the ctime, I found a number of places that update the mtime without a corresponding ctime update. While it's not spelled out explicitly in the POSIX spec, all of the operations that update the mtime must also update the ctime. I've not been able to find any counterexamples, in any case. Some of these patches involve operations not covered by POSIX, but it's still a good idea to update the ctime when updating the mtime. Note that these are largely untested other than for compilation, so please review carefully. These are a preliminary set for the upcoming rework of how we handle the ctime. None of these seem to be very crucial, but it would be nice if various maintainers could pick these up for v6.5. Please let me know if you do, or would rather I shepherd the patch upstream. Jeff Layton (8): ibmvmc: update ctime in conjunction with mtime on write usb: update the ctime as well when updating mtime after an ioctl autofs: set ctime as well when mtime changes on a dir bfs: update ctime in addition to mtime when adding entries efivarfs: update ctime when mtime changes on a write exfat: ensure that ctime is updated whenever the mtime is apparmor: update ctime whenever the mtime changes on an inode cifs: update the ctime on a partial page write drivers/misc/ibmvmc.c | 2 +- drivers/usb/core/devio.c | 16 ++++++++-------- fs/autofs/root.c | 6 +++--- fs/bfs/dir.c | 2 +- fs/efivarfs/file.c | 2 +- fs/exfat/namei.c | 8 ++++---- fs/smb/client/file.c | 2 +- security/apparmor/apparmorfs.c | 7 +++++-- security/apparmor/policy_unpack.c | 11 +++++++---- 9 files changed, 31 insertions(+), 25 deletions(-) -- 2.40.1
