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.
Description of problem:
Paths to all devices on the system is created at the start of a command (saved in "dev-cache"), but while the command is running, some of those device paths may go away. lvm was not detecting and dropping invalid paths in many cases, which could lead to segfaults or other undefined behavior. Also, many places in the lvm code assumed that "dev_name()" always returned an actual device path name, and would attempt to use that path. In fact this function has always been meant for printing messages, and may return "unknown" instead of an actual device path.
An upstream user reported repeatable crashes due to these issues, and reports that the problems are resolved with these fixes:
https://listman.redhat.com/archives/linux-lvm/2022-February/026122.htmlhttps://listman.redhat.com/archives/linux-lvm/2022-April/026151.html
lvm commits in main branch:
cc73d99886df devices: only close PVs on LVs when scan_lvs is enabled
7b1a857d5ac4 devices: use dev-cache aliases handling from label scan functions
4eb04c8c05e5 devices: fix dev_name assumptions
00c3069872ab devices: initial use of existing option
7e70041e324e devices: drop incorrect paths from aliases list
1126be8f8dbc devices: simplify dev_cache_get_by_devt
(cc73d99886df is rhel9-only)
I have not been able to reproduce any of these issues, but based on the code that crashed, and the known problems with that code, we can say that it would be triggered by path names on the system being removed (e.g. devices being removed) while lvm commands were running.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
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 (lvm2 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-2022:7792