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 1511382 - [RHEL-RT] Possible regression with NOHZ_FULL & rt_mutexes in IRQ (BZ1250649) [rhel-7.4.z]
Summary: [RHEL-RT] Possible regression with NOHZ_FULL & rt_mutexes in IRQ (BZ1250649) ...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel-rt
Version: 7.5
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Clark Williams
QA Contact: Jiri Kastner
Marie Dolezelova
Depends On: 1509264
TreeView+ depends on / blocked
Reported: 2017-11-09 09:32 UTC by Oneata Mircea Teodor
Modified: 2017-11-30 16:03 UTC (History)
7 users (show)

Fixed In Version: kernel-rt-3.10.0-693.11.1.rt56.631.el7
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: 1509264
Last Closed: 2017-11-30 16:03:50 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3322 normal SHIPPED_LIVE Moderate: kernel-rt security, bug fix, and enhancement update 2017-11-30 20:18:55 UTC

Description Oneata Mircea Teodor 2017-11-09 09:32:36 UTC
This bug has been copied from bug #1509264 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 10 errata-xmlrpc 2017-11-30 16:03:50 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.