Bug 1400305 – RT kernel panics with dm-multipath enabled [mrg]

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1400305 - RT kernel panics with dm-multipath enabled [mrg]

Summary:	RT kernel panics with dm-multipath enabled [mrg]

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	realtime-kernel (Show other bugs)
Sub Component:
Version:	2.5
Hardware:	x86_64 Linux

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Clark Williams
QA Contact:	Lin Li
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1389215
Blocks:
	Show dependency tree / graph

Reported:	2016-11-30 16:06 EST by Beth Uptagrafft
Modified:	2017-01-17 13:03 EST (History)
CC List:	11 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Cause: An upstream RT commit (fef016306919048a) was missed that made the DM system RT aware. The worker function dm_old_request_fn() was checking to ensure that irqs were disabled, but RT changes how preemption works with spinlocks so the check is invalid on RT. Consequence: Kernel panics on boot when dm-multipath module is loaded. Fix: Apply upstream RT commit fef016306919048a. This commit changes a BUG_ON macro to a BUG_ON_NONRT, which on RT becomes a noop. Result: No panic in when booting a kernel with dm-multipath module enabled.
Story Points:	---
Clone Of:	1389215
Environment:
Last Closed:	2017-01-17 13:03:00 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:0113	normal	SHIPPED_LIVE	Important: kernel-rt security and bug fix update	2017-01-17 17:47:44 EST

Groups: None (edit)

Comment 6 errata-xmlrpc 2017-01-17 13:03:00 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://rhn.redhat.com/errata/RHSA-2017-0113.html

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