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.

The crash looks like:

(gdb) bt
#0  __strchr_sse42 () at ../sysdeps/x86_64/multiarch/strchr.S:136
#1  0x00007f41bf8af7bd in buffer_append_vf (buf=buf@entry=0x7f41bc91b7b0, 
    ap=ap@entry=0x7f41bc91b788) at config-util.c:36
#2  0x00007f41bf8acd75 in daemon_reply_simple (
    id=id@entry=0x7f41bf8aff5f "token_mismatch") at daemon-server.c:411
(gdb) frame 1
#1  0x00007f41bf8af7bd in buffer_append_vf (buf=buf@entry=0x7f41bc91b7b0, 
    ap=ap@entry=0x7f41bc91b788) at config-util.c:36
36			if (!strchr(next, '=')) {
(gdb) p next
$1 = 0x500000000 <Address 0x500000000 out of bounds>

  The reason is that it loops getting a char* varargs
argument until finding a NULL, that is not passed by
the call in daemons/lvmetad/lvmetad-core.c:

                return daemon_reply_simple("token_mismatch",
                                           "expected = %s", state->token,
                                           "received = %s", token,
                                           "update_pid = " FMTd64, (int64_t)state->update_pid,
                                           "reason = %s", "another command has populated the lvmetad cache");

thanks, fixed in
https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=c459f23565e86eb9a8a116995cda7dcaed858b9f

*** Bug 1384914 has been marked as a duplicate of this bug. ***

Marking verified (SanityOnly) in the latest rpms.

3.10.0-677.el7.x86_64
lvm2-2.02.171-4.el7    BUILT: Wed Jun  7 09:16:17 CDT 2017
lvm2-libs-2.02.171-4.el7    BUILT: Wed Jun  7 09:16:17 CDT 2017
lvm2-cluster-2.02.171-4.el7    BUILT: Wed Jun  7 09:16:17 CDT 2017
device-mapper-1.02.140-4.el7    BUILT: Wed Jun  7 09:16:17 CDT 2017
device-mapper-libs-1.02.140-4.el7    BUILT: Wed Jun  7 09:16:17 CDT 2017
device-mapper-event-1.02.140-4.el7    BUILT: Wed Jun  7 09:16:17 CDT 2017
device-mapper-event-libs-1.02.140-4.el7    BUILT: Wed Jun  7 09:16:17 CDT 2017
device-mapper-persistent-data-0.7.0-0.1.rc6.el7    BUILT: Mon Mar 27 10:15:46 CDT 2017


I played around with vg meta data changes using differing global_filter overrides on the command line than what was in the .conf file and saw no crash.

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, 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-2017:2222