Bug 146479

Summary:	pids with held posix locks on gfs/gulm didn't drop on signals.
Product:	[Retired] Red Hat Cluster Suite	Reporter:	michael conrad tadpol tilstra <mtilstra>
Component:	gulm	Assignee:	Chris Feist <cfeist>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	cluster-maint
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:	2010-01-04 19:06:44 UTC	Type:	---
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 conrad tadpol tilstra 2005-01-28 18:30:32 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803

Description of problem:
if a pid on gfs was holding posix range locks and the process died from a signal, the posix range lock was not released.  Later, other processes that might try to get the same lock would fail or block forever.  A cluster reset was required to get out of this.

Version-Release number of selected component (if applicable):
cvs head and rhel4 branch

How reproducible:
Always

Steps to Reproduce:
plock, kill, damn.

Additional info:

Comment 1 michael conrad tadpol tilstra 2005-01-28 18:43:54 UTC

Easy enough fix.  actually just had the state inverted.  Wasn't calling the
upside posix lock update function when I should have been.  Do that right, and
this bug is gone.

Comment 2 Lon Hohberger 2010-01-04 19:06:44 UTC

I believe this was fixed about 5 years ago, but was never added to any erratum.