Bug 1509021 - [MRG-RT] Possible regression with NOHZ_FULL & rt_mutexes in IRQ (BZ1250649)
Summary: [MRG-RT] Possible regression with NOHZ_FULL & rt_mutexes in IRQ (BZ1250649)
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-kernel
Version: 2.5
Hardware: x86_64
OS: Linux
Target Milestone: ---
: ---
Assignee: Clark Williams
QA Contact: Jiri Kastner
Marie Hornickova
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-02 17:11 UTC by Daniel Bristot de Oliveira
Modified: 2021-09-09 12:47 UTC (History)
3 users (show)

Fixed In Version: kernel-rt-3.10.0-693.11.1.rt56.596.el6rt
Doc Type: Bug Fix
Doc Text:
In the realtime kernel, if the rt_mutex locking mechanism was taken in the interrupt context, the normal priority inheritance protocol incorrectly identified a deadlock, and a kernel panic occurred. This update reverts the patch that added rt_mutex in the interrupt context, and the kernel no longer panics due to this behavior.
Clone Of:
Last Closed: 2017-11-30 13:15:53 UTC
Target Upstream Version:

Attachments (Terms of Use)
[PATCH] re-apply Revert "timers: do not raise softirq (5.06 KB, application/mbox)
2017-11-03 09:50 UTC, Daniel Bristot de Oliveira
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3231811 0 None None None 2017-11-03 12:23:09 UTC
Red Hat Product Errata RHSA-2017:3295 0 normal SHIPPED_LIVE Moderate: kernel-rt security and bug fix update 2017-11-30 18:14:28 UTC

Comment 1 Daniel Bristot de Oliveira 2017-11-03 09:50:38 UTC
Created attachment 1347234 [details]
[PATCH] re-apply Revert "timers: do not raise softirq


Comment 7 errata-xmlrpc 2017-11-30 13:15:53 UTC
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.


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