Bug 761865 (GLUSTER-133) - posix_getxattr doesn't handle 'glusterfs.content' key
Summary: posix_getxattr doesn't handle 'glusterfs.content' key
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-133
Product: GlusterFS
Classification: Community
Component: posix
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-13 18:57 UTC by Amar Tumballi
Modified: 2013-12-19 00:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTA
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.