Bug 961506

Summary:	getfattr can hang when trying to get an attribute that doesn't exist
Product:	[Community] GlusterFS	Reporter:	Michael Brown <michael>
Component:	fuse	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3.1	CC:	bugs, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-14 19:40:31 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:

Description Michael Brown 2013-05-09 18:45:13 UTC

Description of problem:
getfattr will hang

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

How reproducible:
100%

Steps to Reproduce:
1. Configure replicated volume
2. mount via fuse
3. sudo getfattr -d -e hex /fuse/filename -n trusted.afr
  
Actual results:
getfattr hangs

Expected results:
trusted.afr: No such attribute

Additional info:
[global.callpool.stack.1.frame.1]
ref_count=1
translator=fuse
complete=0

[global.callpool.stack.1.frame.2]
ref_count=0
translator=gv0-replicate-7
complete=0
parent=gv0-dht
wind_from=dht_getxattr
wind_to=subvol->fops->getxattr
unwind_to=dht_getxattr_cbk

[global.callpool.stack.1.frame.3]
ref_count=1
translator=gv0-dht
complete=0
parent=gv0-write-behind
wind_from=default_getxattr
wind_to=FIRST_CHILD(this)->fops->getxattr
unwind_to=default_getxattr_cbk

[global.callpool.stack.1.frame.4]
ref_count=1
translator=gv0-write-behind
complete=0
parent=gv0-read-ahead
wind_from=default_getxattr
wind_to=FIRST_CHILD(this)->fops->getxattr
unwind_to=default_getxattr_cbk

Comment 1 Niels de Vos 2014-11-27 14:54:25 UTC

The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.