Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 242759 - Glock leak in gfs_create
Glock leak in gfs_create
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gfs-kmod (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Wendy Cheng
GFS Bugs
Depends On:
  Show dependency treegraph
Reported: 2007-06-05 13:28 EDT by Wendy Cheng
Modified: 2010-01-11 22:26 EST (History)
0 users

See Also:
Fixed In Version: RHBA-2007-0577
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 15:07:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:0577 normal SHIPPED_LIVE gfs-kmod bug fix update 2007-10-30 11:36:56 EDT

  None (edit)
Description Wendy Cheng 2007-06-05 13:28:23 EDT
Description of problem:
Bump into this problem while debugging bug #236565 (GFS SPECsfs panic).
Apparently a minor oversight while adding new functionality into GFS for 
RHEL5. GFS versions <= RHEL4 is immuned from this issue.

Upon memory pressure, VM starts to purge inode cache entries that would
fail gfs iget. GFS1 flags this error as "ENOMEM" but returns from gfs_create
call without releasing the glock.

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

How reproducible:
Under memory pressure when vm starts to purge inode cache. 

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Wendy Cheng 2007-06-05 14:57:55 EDT
Patch checked into CVS - move bug into modified state. 
Comment 5 errata-xmlrpc 2007-11-07 15:07:07 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.