summaryrefslogtreecommitdiffstats
path: root/xlators/storage/bd
diff options
context:
space:
mode:
authorPranith Kumar K <pkarampu@redhat.com>2015-01-12 12:50:50 +0530
committerRaghavendra Bhat <raghavendra@redhat.com>2015-01-12 21:56:54 -0800
commitf91d19a9ce6ec6659c84c3f907ebc3ecaceba176 (patch)
treeddf981074156659577262a1b4e359a2b2ceab910 /xlators/storage/bd
parent3971315248c57386e05e6c8f57369a4571555cb2 (diff)
storage/posix: Set gfid after all xattrs, uid/gid are set
Problem: When a new entry is created gfid is set even before uid/gid, xattrs are set on the entry. This can lead to dht/afr healing that file/dir with the uid/gid it sees just after the gfid is set, i.e. root/root. Sometimes setattr/setxattr are failing on that file/dir. Fix: Set gfid of the file/directory only after uid/gid, xattrs are setup properly. Readdirp, lookup either wait for the gfid to be assigned to the entry or not update the in-memory inode ctx in posix-acl xlator which was producing lot EACCESS/EPERM to the application or dht/afr self-heals. Change-Id: I0a6ced579daabe3452f5a85010a00ca6e8579451 BUG: 1088649 Signed-off-by: Pranith Kumar K <pkarampu@redhat.com> Reviewed-on: http://review.gluster.org/9434 Reviewed-by: Niels de Vos <ndevos@redhat.com> Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com> Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
Diffstat (limited to 'xlators/storage/bd')
0 files changed, 0 insertions, 0 deletions