Bug 1510837

Summary: Segfault when reading all_devs device with no_path_retry 4 [rhel-7.4.z]
Product: Red Hat Enterprise Linux 7 Reporter: Oneata Mircea Teodor <toneata>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED ERRATA QA Contact: Lin Li <lilin>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.3CC: agk, bmarzins, bmcclain, heinzm, jbrassow, lilin, lmiksik, loberman, mgandhi, msnitzer, nsoffer, prajnoha, rhandlin, vanhoof, ylavi
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: device-mapper-multipath-0.4.9-111.el7.1 Doc Type: Bug Fix
Doc Text:
Previously, the DM Multipath service terminated unexpectedly when it attempted to add a feature to the features string of a built-in device configuration that had no features string. With this update, DM Multipath first checks if the features string exists, and creates one if necessary. As a result, DM Multipath no longer crashes when trying to modify a nonexistent features string.
Story Points: ---
Clone Of: 1459370 Environment:
Last Closed: 2018-01-25 11:39:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1459370    
Bug Blocks: 1335176    

Description Oneata Mircea Teodor 2017-11-08 10:16:30 UTC
This bug has been copied from bug #1459370 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 2 Ben Marzinski 2017-11-08 23:28:36 UTC
features fix backported.

Comment 9 errata-xmlrpc 2018-01-25 11:39:30 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.

https://access.redhat.com/errata/RHEA-2018:0142

Comment 10 Nir Soffer 2018-02-05 07:21:17 UTC
Ben, is this fix available in Fedora 27?

Comment 11 Ben Marzinski 2018-02-06 14:41:50 UTC
Yes, the code to fix this is in f27.