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:
I experienced a segfault in pvs, very likely caused by corrupted message served by lvmetad.

There were about 19 instances of pvs with different options running at the same time.

Likely a race condition in lvmetad. The issue is not reproducible, though it affected two clients running at the same time both of them got response with large part of metadata replaced by two characters.

Version-Release number of selected component (if applicable):
lvm2-2.02.97-0.151

How reproducible:
low reproducibility

Steps to Reproduce:
1. test was running multiple pvs with various combinations of -o and -O
  
Actual results:
incorrect response from lvmetad served to clients

Expected results:
correct metadata should be served

Additional info:
I let running 19 concurrent cycles running pvs for all night and could not reproduce the issue.

Created attachment 601952 [details]
the message served by lvmetad

I reviewed the routine receiving data from socket, and could not find a problem there, thus I believe the data vere served by lvmetad.

Remaining pvs running at the same time were either finished correctly or were killed by test.

One more pvs command was issued afterwards and returned correct result.

Issue is not reproducible - I have not seen it since reported.

Also since Bug 845269 was fixed the severity of the bug is low.