diff options
| author | Kinglong Mee <kinglongmee@gmail.com> | 2019-08-05 11:08:02 +0800 |
|---|---|---|
| committer | hari gowtham <hari.gowtham005@gmail.com> | 2019-08-07 05:09:15 +0000 |
| commit | cf42677ac0cc042ea4318062219908095d4027c0 (patch) | |
| tree | 112ba82429ef6ca00fe00d0810fb6fab64708635 /doc/release-notes | |
| parent | aa45fcc1384ea6120d582cdad35b1d610e6437af (diff) | |
features/utime: always update ctime at setattr
For the nfs EXCLUSIVE mode create may sets a later time
to mtime (at verifier), it should not set to ctime for
storage.ctime does not allowed set ctime to a earlier time.
/* Earlier, mdata was updated only if the existing time is less
* than the time to be updated. This would fail the scenarios
* where mtime can be set to any time using the syscall. Hence
* just updating without comparison. But the ctime is not
* allowed to changed to older date.
*/
According to kernel's setattr, always set ctime at setattr,
and doesnot set ctime from mtime at storage.ctime.
Backport of:
> Patch: https://review.gluster.org/23154
> Change-Id: I5cfde6cb7f8939da9617506e3dc80bd840e0d749
> BUG: 1737288
> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
Change-Id: I5cfde6cb7f8939da9617506e3dc80bd840e0d749
fixes: bz#1737746
Signed-off-by: Kotresh HR <khiremat@redhat.com>
Diffstat (limited to 'doc/release-notes')
0 files changed, 0 insertions, 0 deletions