Bug 1086949 - If multipathd is reconfigured before it starts completely up, it will crash.
Summary: If multipathd is reconfigured before it starts completely up, it will crash.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: device-mapper-multipath
Version: 5.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ben Marzinski
QA Contact: Storage QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-12 01:38 UTC by Ben Marzinski
Modified: 2014-09-16 00:21 UTC (History)
12 users (show)

Fixed In Version: device-mapper-multipath-0.4.7-62.el5
Doc Type: Bug Fix
Doc Text:
Cause: Multipathd wasn't blocking the SIGHUP signal on startup. This means that multipathd could receive a sighup and try to reconfigure before it was completely set up Consequence: Multipathd would crash with a segfault if "service multipathd reload" was run immediately after it started, since the reconfigure code assumes that it is already set up. Fix: Multipathd now blocks the SIGHUP signal until it has completed initialization Result: Multipathd no longer crashes if it receives a sighup signal from "service multipathd reload" immediately after it starts.
Clone Of:
Environment:
Last Closed: 2014-09-16 00:21:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1228 0 normal SHIPPED_LIVE device-mapper-multipath bug fix update 2014-09-16 04:15:04 UTC

Description Ben Marzinski 2014-04-12 01:38:05 UTC
Description of problem:
multipathd doesn't block the sighup signal on start-up. If it receives one after it has set up the signal handler, but before it has finished configuring itself, it will crash, because the reconfigure signal handler assumes that the daemon is all the way set up.

Version-Release number of selected component (if applicable):
All RHEL5 packages

How reproducible:
Virtually every time

Steps to Reproduce:
1. with multipathd stopped, run

# multipathd; service multipathd reload

Actual results:
Multipathd crashes with a segfault

Expected results:
Multipathd doesn't crash

Additional info:
I already have a fix for this issue.

Comment 1 RHEL Program Management 2014-04-12 01:58:12 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 3 Barry Donahue 2014-07-11 17:54:35 UTC
# multipathd; service multipathd reload
Reloading multipathd:                                      [  OK  ]

Comment 5 errata-xmlrpc 2014-09-16 00:21:26 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.

http://rhn.redhat.com/errata/RHBA-2014-1228.html


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