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.

Description of problem:
multipathd[4401]: segfault at 7faf8e4b986c ip 00007faf90fe3a9f sp 00007faf92a795e0 error 4 in libgcc_s-8-20191121.so.1[7faf90fd4000+17000]

Version-Release number of selected component (if applicable):
device-mapper-multipath-0.8.3-3.el8.x86_64

How reproducible:
once

Steps to Reproduce:
1. 
run task :/kernel/storage/multipath/shutdown_race_BZ_639429 
 multipathd shutdown test round 26
 stop multipathd.service
 start multipathd.service
2.
3.

Actual results:
FAIL: Found segfault of multipathd
Feb 26 07:13:45 dell-per430-17 kernel: multipathd[4401]: segfault at 7faf8e4b986c ip 00007faf90fe3a9f sp 00007faf92a795e0 error 4 in libgcc_s-8-20191121.s

Expected results:
No segfault

Additional info:
beaker job:https://beaker.engineering.redhat.com/recipes/7948440#task106737622
test log: https://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2020/02/40955/4095573/7948440/106737633/taskout.log

In your tests, is the system set up to capture coredumps on segfaults, and if so, did you capture the segfault? Segfaults are much easier to debug with a coredump.

At any rate, I'll try to reproduce this myself.

I have tried to recreate this repeatedly on my machines, but haven't been able to.  If you can reproduce this and get me a coredump, or even a backtrace, that would be helpful.

ok. I will try to get the coredump once I reproduce it.

*** This bug has been marked as a duplicate of bug 1875384 ***