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.
Filtering with regular expressions (for example when using lvm commands to filter devices) could have failed. This was due to an error in removing a common suffix. With this update, the optimization for common suffixes works correctly.
Description of problem:
Some filters filter devices wrongly.
The original cmd:
/sbin/pvs --config " devices { preferred_names = [\"^/dev/mapper/\"] write_cache_state=0 filter = [ \"a%/dev/mapper/36000402004ec06f56089aa1400000000|/dev/mapper/36000402004ec06f56089ab3a00000000|/dev/mapper/36000402004ec06f5608a865500000000%\", \"r%.*%\" ] } "
This is an irc log excerpt that shows agk trying to narrow down the issue.
[Tuesday 12 October 2010] [19:03:01] <agk> so it's do with pulling the suffix out
[Tuesday 12 October 2010] [19:03:12] <agk> /sbin/pvs --config " devices { write_cache_state=0 filter = [ \"a%8(9aa140000000|9ab3a0000000|a86550)%\", \"r%.*%\" ] } "
[Tuesday 12 October 2010] [19:03:15] <agk> vs
[Tuesday 12 October 2010] [19:03:26] <agk> /sbin/pvs --config " devices { write_cache_state=0 filter = [ \"a%8(9aa140000000|9ab3a0000000|a8655)%\", \"r%.*%\" ] } "
[Tuesday 12 October 2010] [19:03:44] <agk> removing that last '0' it starts to work again
[Tuesday 12 October 2010] [19:04:51] <agk> So the simplest case so far:
[Tuesday 12 October 2010] [19:04:56] <agk> "a%8(9aa140|9ab3a0|a86550)%\ fails
[Tuesday 12 October 2010] [19:05:11] <agk> a%8(9aa140|9ab3a|a86550)%\
[Tuesday 12 October 2010] [19:05:12] <agk> works
[Tuesday 12 October 2010] [19:05:36] <agk> so it must be going wrong when it sees a common suffix (0) and pulls it out of the expression
[Tuesday 12 October 2010] [19:06:30] <agk> but if there are only 2 things instead of 3 between the |s it works ok
[Tuesday 12 October 2010] [19:10:48] <agk> So: /tmp/bothcmd2 is my simplest test case so far
[Tuesday 12 October 2010] [19:10:55] <agk> bothcmds2
[Tuesday 12 October 2010] [19:11:07] <agk> it runs two supposedly identical cmds but gets different output
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Well the conclusion from irc was that removing a common suffix was broken.
But other parts of this code were changed since that was added, so we might find rather than fixing that, removing it no longer makes any noticeable performance difference.
So (1) try removing that optimisation and see how much it slows things down;
or (2) try to fix the optimisation.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Filtering with regular expressions (for example when using lvm commands to filter devices) could have failed. This was due to an error in removing a common suffix. With this update, the optimization for common suffixes works correctly.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0772.html
Description of problem: Some filters filter devices wrongly. The original cmd: /sbin/pvs --config " devices { preferred_names = [\"^/dev/mapper/\"] write_cache_state=0 filter = [ \"a%/dev/mapper/36000402004ec06f56089aa1400000000|/dev/mapper/36000402004ec06f56089ab3a00000000|/dev/mapper/36000402004ec06f5608a865500000000%\", \"r%.*%\" ] } " This is an irc log excerpt that shows agk trying to narrow down the issue. [Tuesday 12 October 2010] [19:03:01] <agk> so it's do with pulling the suffix out [Tuesday 12 October 2010] [19:03:12] <agk> /sbin/pvs --config " devices { write_cache_state=0 filter = [ \"a%8(9aa140000000|9ab3a0000000|a86550)%\", \"r%.*%\" ] } " [Tuesday 12 October 2010] [19:03:15] <agk> vs [Tuesday 12 October 2010] [19:03:26] <agk> /sbin/pvs --config " devices { write_cache_state=0 filter = [ \"a%8(9aa140000000|9ab3a0000000|a8655)%\", \"r%.*%\" ] } " [Tuesday 12 October 2010] [19:03:44] <agk> removing that last '0' it starts to work again [Tuesday 12 October 2010] [19:04:51] <agk> So the simplest case so far: [Tuesday 12 October 2010] [19:04:56] <agk> "a%8(9aa140|9ab3a0|a86550)%\ fails [Tuesday 12 October 2010] [19:05:11] <agk> a%8(9aa140|9ab3a|a86550)%\ [Tuesday 12 October 2010] [19:05:12] <agk> works [Tuesday 12 October 2010] [19:05:36] <agk> so it must be going wrong when it sees a common suffix (0) and pulls it out of the expression [Tuesday 12 October 2010] [19:06:30] <agk> but if there are only 2 things instead of 3 between the |s it works ok [Tuesday 12 October 2010] [19:10:48] <agk> So: /tmp/bothcmd2 is my simplest test case so far [Tuesday 12 October 2010] [19:10:55] <agk> bothcmds2 [Tuesday 12 October 2010] [19:11:07] <agk> it runs two supposedly identical cmds but gets different output Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: