diff options
| author | luneo7 <luneo7@gmail.com> | 2017-10-10 17:08:22 -0300 |
|---|---|---|
| committer | Lucas Ferreira <luneo7@gmail.com> | 2017-10-25 14:07:19 +0000 |
| commit | 80fbfef5c70b67838a391041e80a67e41c9142b6 (patch) | |
| tree | 248d410e4de7de9320fb057cf09fbfe9dddb2fb2 /glusterfsd | |
| parent | 7d72d5de2f978db30072f72caa559c1f5f543ef6 (diff) | |
features/worm: Adding check to newloc when doing rename
Problem: Since rename didn't check if newloc exists and it's
retention state it was possible to rename a new file that wasn't
in retention over a existing file that was in read-only state.
Cherry picked from commit 00a4dc0:
> Change-Id: I63c6bbabb7bb456ebedf201cc77b878ffda62229
> BUG: 1484490
> Signed-off-by: luneo7 <luneo7@gmail.com>
> Reviewed-on: https://review.gluster.org/18104
> Tested-by: jiffin tony Thottan <jthottan@redhat.com>
> Tested-by: Prashanth Pai <ppai@redhat.com>
> Smoke: Gluster Build System <jenkins@build.gluster.org>
> CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
> Reviewed-by: Prashanth Pai <ppai@redhat.com>
> Reviewed-by: Karthik U S <ksubrahm@redhat.com>
> Reviewed-by: Amar Tumballi <amarts@redhat.com>
Change-Id: I63c6bbabb7bb456ebedf201cc77b878ffda62229
BUG: 1484489
Signed-off-by: luneo7 <luneo7@gmail.com>
Diffstat (limited to 'glusterfsd')
0 files changed, 0 insertions, 0 deletions