Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 159615

Summary: cman schedules within spinlock
Product: [Retired] Red Hat Cluster Suite Reporter: David Teigland <teigland>
Component: cmanAssignee: Christine Caulfield <ccaulfie>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: https://www.redhat.com/archives/linux-cluster/2005-June/msg00005.html
Whiteboard:
Fixed In Version: RHBA-2005-734 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-07 16:46:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description David Teigland 2005-06-06 03:46:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2

Description of problem:
Cman barrier callback into SM schedules within spinlock.
The schedule is hidden within the SM_RETRY/kmalloc macro
which doesn't make sense anyway when using GFP_ATOMIC.

I don't think we've actually seen this cause a problem
apart from the warning message, but the potential of
deadlocking the kernel obviously exists.


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


How reproducible:
Always

Steps to Reproduce:
1. use cman
2.
3.
  

Additional info:

Comment 1 Christine Caulfield 2005-06-28 13:15:25 UTC
This was fixed on the RHEL4 branch on 2005/06/06

Comment 3 Red Hat Bugzilla 2005-10-07 16:46:30 UTC
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.

http://rhn.redhat.com/errata/RHBA-2005-734.html