Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1509021 - [MRG-RT] Possible regression with NOHZ_FULL & rt_mutexes in IRQ (BZ1250649)
[MRG-RT] Possible regression with NOHZ_FULL & rt_mutexes in IRQ (BZ1250649)
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-kernel (Show other bugs)
2.5
x86_64 Linux
unspecified Severity urgent
: ---
: ---
Assigned To: Clark Williams
Jiri Kastner
Marie Dolezelova
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-02 13:11 EDT by Daniel Bristot de Oliveira
Modified: 2018-03-12 10:25 EDT (History)
3 users (show)

See Also:
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.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-30 08:15:53 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


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


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3231811 None None None 2017-11-03 08:23 EDT
Red Hat Product Errata RHSA-2017:3295 normal SHIPPED_LIVE Moderate: kernel-rt security and bug fix update 2017-11-30 13:14:28 EST

  None (edit)
Comment 1 Daniel Bristot de Oliveira 2017-11-03 05:50 EDT
Created attachment 1347234 [details]
[PATCH] re-apply Revert "timers: do not raise softirq

Patch
Comment 7 errata-xmlrpc 2017-11-30 08:15:53 EST
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.

https://access.redhat.com/errata/RHSA-2017:3295

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