[Bugs] [Bug 1248325] quota: In enforcer, caching parents in ctx during build ancestry is not working
bugzilla at redhat.com
bugzilla at redhat.com
Mon Aug 3 04:04:47 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1248325
--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11799 committed in release-3.7 by Raghavendra
G (rgowdapp at redhat.com)
------
commit 998a63357cb186953d0eedf5a06bc4ac5594674d
Author: vmallika <vmallika at redhat.com>
Date: Wed Jul 22 09:02:39 2015 +0530
quota: fix parents caching during build ancestry
This is a backport of http://review.gluster.org/#/c/11574/
In build ancestry, we get the list of parents for a file,
these parents are cached in inode ctx.
This caching is not happening because posix is not setting
d_stat information in the leaf node entry
This patch fixes the issue
Inode-ctx is not updated with new parent when
rename performed on same directory.
This patch fixes the issue
There is a possibility of caching stale entries,
consider below example:
1) build_ancestry invoked on a file
2) rename is invoked on the same file
3) buils_ancestry prepared entries of old parent
4) rename completed and in cbk old parent is replaced with
new parent in inode ctx
5) now build_ancestry cbk adds old parent to inode ctx
In this patch we also remove stale entries in writev and fallocate
> Change-Id: Ib1854a41b47b14eb775326588352015c83d034de
> BUG: 1240949
> Signed-off-by: vmallika <vmallika at redhat.com>
> Reviewed-on: http://review.gluster.org/11574
> Tested-by: Gluster Build System <jenkins at build.gluster.com>
> Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
Change-Id: I26a196e7eeed343593bea3a0b7b51d7be12500a3
BUG: 1248325
Signed-off-by: vmallika <vmallika at redhat.com>
Reviewed-on: http://review.gluster.org/11799
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=qj5uDgf7Rh&a=cc_unsubscribe
More information about the Bugs
mailing list