Bug 762764 (GLUSTER-1032)

Summary:	Set lock-owner with pid when fuse does not supply value
Product:	[Community] GlusterFS	Reporter:	Pavan Vilas Sondur <pavan>
Component:	replicate	Assignee:	Pavan Vilas Sondur <pavan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	urgent
Version:	mainline	CC:	gluster-bugs, vijay
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:	RTP	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Pavan Vilas Sondur 2010-06-27 16:25:56 UTC

In afr transactions and self heal, some fops do not have frame->root->lk_owner set as FUSE does not set values for all FOPs. Set it with pid values to carry with sane lock-owner values for inodelks/entrylks.

Test Plan:
* Run posix test suite and turn on option 'option trace on' in locks xlator. All lk-owner values should have positive values (no zeros)

* Run self heal tests and verify non-zero lk-owner values just like described above.

Comment 1 Anand Avati 2010-06-29 06:58:07 UTC

PATCH: http://patches.gluster.com/patch/3497 in release-3.0 (cluster/afr: Set lk-owner to pid when fuse does not supply it.)