Bug 159615 - cman schedules within spinlock
cman schedules within spinlock
Status: CLOSED ERRATA
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: cman (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Christine Caulfield
Cluster QE
https://www.redhat.com/archives/linux...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-05 23:46 EDT by David Teigland
Modified: 2009-04-16 15:59 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHBA-2005-734
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-07 12:46:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Teigland 2005-06-05 23:46:14 EDT
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 09:15:25 EDT
This was fixed on the RHEL4 branch on 2005/06/06
Comment 3 Red Hat Bugzilla 2005-10-07 12:46:30 EDT
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

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