diff options
| author | Jeff Layton <jlayton@kernel.org> | 2023-09-13 09:33:12 -0400 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2023-09-25 14:53:54 +0200 |
| commit | 03dbab3bba5f009d053635c729d1244f2c8bad38 (patch) | |
| tree | 2af20d00bcd403a543fc23b74faf382157823a00 /fs/overlayfs | |
| parent | 493c71926c20309226b6d73f6b661a9813de5f0b (diff) | |
| download | linux-stable-03dbab3bba5f009d053635c729d1244f2c8bad38.tar.gz linux-stable-03dbab3bba5f009d053635c729d1244f2c8bad38.tar.bz2 linux-stable-03dbab3bba5f009d053635c729d1244f2c8bad38.zip | |
overlayfs: set ctime when setting mtime and atime
Nathan reported that he was seeing the new warning in
setattr_copy_mgtime pop when starting podman containers. Overlayfs is
trying to set the atime and mtime via notify_change without also
setting the ctime.
POSIX states that when the atime and mtime are updated via utimes() that
we must also update the ctime to the current time. The situation with
overlayfs copy-up is analogies, so add ATTR_CTIME to the bitmask.
notify_change will fill in the value.
Reported-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Tested-by: Nathan Chancellor <nathan@kernel.org>
Acked-by: Christian Brauner <brauner@kernel.org>
Acked-by: Amir Goldstein <amir73il@gmail.com>
Message-Id: <20230913-ctime-v1-1-c6bc509cbc27@kernel.org>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'fs/overlayfs')
| -rw-r--r-- | fs/overlayfs/copy_up.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/overlayfs/copy_up.c b/fs/overlayfs/copy_up.c index bae404a1bad4..557e46bc4361 100644 --- a/fs/overlayfs/copy_up.c +++ b/fs/overlayfs/copy_up.c @@ -337,7 +337,7 @@ static int ovl_set_timestamps(struct ovl_fs *ofs, struct dentry *upperdentry, { struct iattr attr = { .ia_valid = - ATTR_ATIME | ATTR_MTIME | ATTR_ATIME_SET | ATTR_MTIME_SET, + ATTR_ATIME | ATTR_MTIME | ATTR_ATIME_SET | ATTR_MTIME_SET | ATTR_CTIME, .ia_atime = stat->atime, .ia_mtime = stat->mtime, }; |