Bug 761865 (GLUSTER-133)

Summary: posix_getxattr doesn't handle 'glusterfs.content' key
Product: [Community] GlusterFS Reporter: Amar Tumballi <amarts>
Component: posixAssignee: Amar Tumballi <amarts>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: gluster-bugs, vinayak, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTA Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Amar Tumballi 2009-07-13 18:57:00 UTC 
currently 'trusted.glusterfs.content' key is handled only in lookup, but is not handled in getxattr. Instead if one tries to fetch the data with this key, there is a huge memory leak (as content is read from the file, but not set in dictionary or freed later).
Comment 1 Amar Tumballi 2009-11-11 17:54:56 UTC 
This bug is 'invalid' as posix_getxattr () will never gets a key 'glusterfs.content', instead it gets call on trusted.* or user.* 

No need to handle this. Marking closed.