Description of problem: In the past, GFS2 has had a history of glock locking problems. Most of these problems have been due to GFS2 bugs, but in order to debug these issues, it's important for us to determine whether or not GFS2 has received its callback from the lock manager, DLM. For RHEL6 and upstream, we have GFS2 trace points we can use to determine whether we received the callback. Since the RHEL5 kernel has no infrastructure for trace points, we need a flag in the glock dump to tell us. Version-Release number of selected component (if applicable): RHEL5 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: The need for the new flag was established as part of bug #694669
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Created attachment 497865 [details] Initial patch
I posted the final patch to rhkernel-list for inclusion into 5.7. Changing status to POST.
Patch(es) available in kernel-2.6.18-261.el5 You can download this test kernel (or newer) from http://people.redhat.com/jwilson/el5 Detailed testing feedback is always welcomed.
Confirmed patch is in -264.el5.
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 therefore 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. http://rhn.redhat.com/errata/RHSA-2011-1065.html