Bug 799399
Summary: | ftrace_dump() can cause issues on RT | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Steven Rostedt <srostedt> | ||||
Component: | realtime-kernel | Assignee: | John Kacur <jkacur> | ||||
Status: | CLOSED ERRATA | QA Contact: | David Sommerseth <davids> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 2.2 | CC: | bhu, jkacur, jkastner, lgoncalv, ovasik | ||||
Target Milestone: | 2.2 | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Cause: RT in_atomic only checks preempt_count
Consequence: RT can grab the lock even if irqs are disabled, and cause a scheduling while atomic
Fix: Check if interrupts are disabled before giving the OK to grab the ring buffer reader lock.
Result: The ring buffer reader lock works correctly
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-09-19 18:03:39 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Steven Rostedt
2012-03-02 16:31:41 UTC
Created attachment 567106 [details]
Also check for interrupts disabled in ring buffer grabbing read lock
In RT, check if interrupts are disabled before giving the OK to grab the ring buffer reader lock.
This fix is equivalent to 9922864 git describe --contains 9922864 v3.2.14-rt24~9 Adding note to kernel-rt.spec Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: RT in_atomic only checks preempt_count Consequence: RT can grab the lock even if irqs are disabled, and cause a scheduling while atomic Fix: Check if interrupts are disabled before giving the OK to grab the ring buffer reader lock. Result: The ring buffer reader lock works correctly Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-1282.html |