Bug 1304350

Summary: access-control : spurious error log message on every setxattr call
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Rahul Hinduja <rhinduja>
Component: geo-replicationAssignee: Jiffin <jthottan>
Status: CLOSED CURRENTRELEASE QA Contact: Rochelle <rallan>
Severity: medium Docs Contact:
Priority: medium    
Version: rhgs-3.1CC: avishwan, bugs, chrisw, csaba, jthottan, nlevinki, rallan, rhinduja, sanandpa
Target Milestone: ---Keywords: EasyFix, Triaged, ZStream
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1303501 Environment:
Last Closed: 2018-04-16 15:58:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1303501, 1308800    
Bug Blocks:    

Description Rahul Hinduja 2016-02-03 11:57:08 UTC 
+++ This bug was initially created as a clone of Bug #1303501 +++

Description of problem:

Spurious log message is filled in gluster logs on every setxattr call. This is due to a check is missed before calling the handling_other_acl_related_xattr() in
posix_acl_setxattr_cbk()

Version-Release number of selected component (if applicable):
mainline


Additional info 

log message :
[2016-01-31 17:38:48.027792] I [dict.c:473:dict_get] (-->/usr/lib/x86_64-linux-gnu/glusterfs/3.7.6/xlator/system/posix-acl.so(posix_acl_setxattr_cbk+0x26) [0x7f2334c5c166] -->/usr/lib/x86_64-linux-gnu/glusterfs/3.7.6/xlator/system/posix-acl.so(handling_other_acl_related_xattr+0xb0) [0x7f2334c5c0f0] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(dict_get+0x93) [0x7f233c04b0c3] ) 0-dict: !this || key=system.posix_acl_default [Invalid argument]

--- Additional comment from Vijay Bellur on 2016-02-01 00:45:24 EST ---

REVIEW: http://review.gluster.org/13325 (access-control : remove spurious error message from the posix_setxattr_cbk) posted (#1) for review on master by jiffin tony Thottan (jthottan)
Comment 3 Jiffin 2018-01-11 09:49:14 UTC 
IMO this fix is already part of upstream 3.8, so should be available from 3.2 onwards. So can we please close this bug as "CURRENT RELEASE"