diff options
| author | Kotresh HR <khiremat@redhat.com> | 2018-06-01 01:48:31 -0400 |
|---|---|---|
| committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2018-06-08 12:56:57 +0000 |
| commit | acd9a863e80a7f56e25b3ed151a4711126de3208 (patch) | |
| tree | bcf8474d7661760914fb09341ef145a89385bac6 /xlators/protocol/server/src/server-rpc-fops.c | |
| parent | 9757ee891cf45abd6380fd693639f5c4cd199c2f (diff) | |
posix/ctime: Fix fops racing in updating mtime/atime
In distributed systems, there could be races with fops
updating mtime/atime which could result in different
mtime/atime for same file. So updating them only if
time is greater than the existing makes sure, only
the highest time is retained. If the mtime/atime
update comes from the explicit utime syscall, it is
allowed to set to previous time.
Thanks Xavi for helping in rooting the issue.
Backport of:
> Patch: https://review.gluster.org/#/c/20120/
> BUG: 1584981
> Change-Id: If1230a75b96d7f9a828795189fcc699049e7826e
> Signed-off-by: Kotresh HR <khiremat@redhat.com>
(cherry picked from commit a6f0e7a4f1ca203762cae2ed5e426b52124c74dc)
fixes: bz#1585894
Change-Id: If1230a75b96d7f9a828795189fcc699049e7826e
Signed-off-by: Kotresh HR <khiremat@redhat.com>
Diffstat (limited to 'xlators/protocol/server/src/server-rpc-fops.c')
0 files changed, 0 insertions, 0 deletions