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.
Bug 1913549 - Customer is using libmpathpersist and since updating to device-mapper-multipath-libs-0.8.4-5.el8 is experiencing application coredumps
Summary: Customer is using libmpathpersist and since updating to device-mapper-multipa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: device-mapper-multipath
Version: 8.3
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: 8.0
Assignee: Ben Marzinski
QA Contact: Lin Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-07 04:57 UTC by Lance Digby
Modified: 2021-09-06 15:21 UTC (History)
9 users (show)

Fixed In Version: device-mapper-multipath-0.8.4-8.el8
Doc Type: Bug Fix
Doc Text:
Cause: mpath_persistent_reserve_in and mpath_persistent_reserve_out stopped being thread safe with device-mapper-multipath-0.8.3 Consequence: multithreaded applications that called mpath_persistent_reserve_in or mpath_persistent_reserve_out in multiple threads at the same time could crash. Fix: mpath_persistent_reserve_in and mpath_persistent_reserve_out are now thread safe again Result: multithreaded applications can safely call mpath_persistent_reserve_in and mpath_persistent_reserve_out in multiple threads at the same time.
Clone Of:
Environment:
Last Closed: 2021-05-18 15:06:56 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 3 Ben Marzinski 2021-02-05 15:57:13 UTC 
mpath_persistent_reserve_in and mpath_persistent_reserve_out are now thread safe again.
Comment 18 errata-xmlrpc 2021-05-18 15:06:56 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 (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/RHEA-2021:1685
Note You need to log in before you can comment on or make changes to this bug.