RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 592418 - dlm user lock callback ordering
Summary: dlm user lock callback ordering
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: David Teigland
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-14 20:01 UTC by David Teigland
Modified: 2010-11-15 14:28 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-15 14:28:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
patch (5.27 KB, text/plain)
2010-05-14 20:06 UTC, David Teigland
no flags Details
patch (5.40 KB, application/octet-stream)
2010-05-14 20:07 UTC, David Teigland
no flags Details

Description David Teigland 2010-05-14 20:01:40 UTC
Description of problem:

Bug 568102 fixed a bast/cast callback ordering problem for dlm locks that originate from the kernel.  This bug is to fix the same problem for locks that originate from user space.

The fix has been tested and verified using dlm_load:
http://fedorapeople.org/gitweb?p=teigland/public_git/dct-stuff.git;a=blob_plain;f=dlm/dlm_load.c;hb=HEAD


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 David Teigland 2010-05-14 20:06:27 UTC
Created attachment 414153 [details]
patch

rhel6 patch

Comment 3 David Teigland 2010-05-14 20:07:48 UTC
Created attachment 414154 [details]
patch

rhel6 patch (attached wrong file in prev comment)

Comment 4 David Teigland 2010-05-20 16:16:15 UTC
posted to rhkernel
http://post-office.corp.redhat.com/archives/rhkernel-list/2010-May/msg02171.html

Comment 5 RHEL Program Management 2010-05-20 17:46:28 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 6 Aristeu Rozanski 2010-05-28 20:38:06 UTC
Patch(es) available on kernel-2.6.32-31.el6

Comment 9 releng-rhel@redhat.com 2010-11-15 14:28:47 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. 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.