Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause: If multipathd detects a path's wwid has changed, multipathd wasn't checking if the path belonged to a multipath device before dereferencing the multipath device's alias
Consequence: multipathd could crash if disable_changed_wwids is set, and a path not belonging to a multipath device has a wwid change
Fix: multipathd now checks if a path with a changed wwid belongs to a multipath device, before trying to dereference that device pointer
Result: multipathd no longer crashes when disable_changed_wwids is set, and a path not belonging to a multipath device has its wwid change.
Description of problem:
Customer is running 7.9 and had to enable disable_changed wwids. After enabling this multipathd started coredumping.
Version-Release number of selected component (if applicable):
device-mapper-multipath-0.4.9-134.el7_9.x86_64
How reproducible:
Easy to reproduce at customer
Steps to Reproduce:
1.Enable disable_changed_wwids
2.multipathd segfaults
3.
Actual results:
multipathd segfaults
Expected results:
Known fix needed to prevent this
Additional info:
Analyzing the core file and why multipathd is segfaulting
Program terminated with signal 11, Segmentation fault.
#0 uev_update_path (vecs=0x55ce6e3d7c80, uev=0x7ff2bc000b50) at main.c:859
859 dm_fail_path(pp->mpp->alias, pp->dev_t);
(gdb) list
854 condlog(0, "%s: path wwid changed from '%s' to '%s'. disallowing", uev->kernel, wwid, pp->wwid);
855 strcpy(pp->wwid, wwid);
856 if (!pp->wwid_changed) {
857 pp->wwid_changed = 1;
858 pp->tick = 1;
859 dm_fail_path(pp->mpp->alias, pp->dev_t);
860 }
861 }
862 else {
863 pp->wwid_changed = 0;
(gdb) p pp
$1 = (struct path *) 0x55ce6e402900
(gdb) p pp->mpp->alias
Cannot access memory at address 0x1c0
(gdb) p pp->mpp->alias
Cannot access memory at address 0x1c0
(gdb) p pp->mpp
$2 = (struct multipath *) 0x0
Seems to be a known bug with disable_changed_wwids
https://listman.redhat.com/archives/dm-devel/2017-March/msg00189.html
Its not patched
I will log a BZ to get it patched, but its due to the disable_changed _wwids being enabled
Best Regards
Red Hat
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 (device-mapper-multipath bug fix and enhancement update), 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/RHBA-2021:3333
Description of problem: Customer is running 7.9 and had to enable disable_changed wwids. After enabling this multipathd started coredumping. Version-Release number of selected component (if applicable): device-mapper-multipath-0.4.9-134.el7_9.x86_64 How reproducible: Easy to reproduce at customer Steps to Reproduce: 1.Enable disable_changed_wwids 2.multipathd segfaults 3. Actual results: multipathd segfaults Expected results: Known fix needed to prevent this Additional info: Analyzing the core file and why multipathd is segfaulting Program terminated with signal 11, Segmentation fault. #0 uev_update_path (vecs=0x55ce6e3d7c80, uev=0x7ff2bc000b50) at main.c:859 859 dm_fail_path(pp->mpp->alias, pp->dev_t); (gdb) list 854 condlog(0, "%s: path wwid changed from '%s' to '%s'. disallowing", uev->kernel, wwid, pp->wwid); 855 strcpy(pp->wwid, wwid); 856 if (!pp->wwid_changed) { 857 pp->wwid_changed = 1; 858 pp->tick = 1; 859 dm_fail_path(pp->mpp->alias, pp->dev_t); 860 } 861 } 862 else { 863 pp->wwid_changed = 0; (gdb) p pp $1 = (struct path *) 0x55ce6e402900 (gdb) p pp->mpp->alias Cannot access memory at address 0x1c0 (gdb) p pp->mpp->alias Cannot access memory at address 0x1c0 (gdb) p pp->mpp $2 = (struct multipath *) 0x0 Seems to be a known bug with disable_changed_wwids https://listman.redhat.com/archives/dm-devel/2017-March/msg00189.html Its not patched I will log a BZ to get it patched, but its due to the disable_changed _wwids being enabled Best Regards Red Hat