Bug 146479 - pids with held posix locks on gfs/gulm didn't drop on signals.
Summary: pids with held posix locks on gfs/gulm didn't drop on signals.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: gulm
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chris Feist
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-28 18:30 UTC by michael conrad tadpol tilstra
Modified: 2010-01-04 19:06 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-01-04 19:06:44 UTC
Embargoed:

Attachments (Terms of Use)

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