Bug 1396654 - All lvm commands show cryptic error messages when filter rules definition is very long
Summary: All lvm commands show cryptic error messages when filter rules definition is ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-18 20:57 UTC by Heinz Mauelshagen
Modified: 2017-12-06 11:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 11:54:16 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Heinz Mauelshagen 2016-11-18 20:57:26 UTC
Description of problem:
lvm tools show 

"vsnprintf failed for config line
_log_array_value_used: failed to write node value"

with an extrem long filter definition in /etc/lvm/lvm.conf

Version-Release number of selected component (if applicable):
RHEL6.8

How reproducible:
Always

Steps to Reproduce:
1. Create insane long filter rules
2. Run any lvm command
3.

Actual results:
Aforementioned error messages

Expected results:
Well defined error message like "Your filter rules are too long"

Additional info:

Comment 2 Alasdair Kergon 2016-11-19 03:17:43 UTC
Clear bug: if it's a valid regex it should work regardless of length, not give an error unless the machine runs out of memory.  The filter there is not too long.

Comment 6 Zdenek Kabelac 2016-11-21 09:53:26 UTC
Just a side node - for better and more efficient usage could be here to rather define  'accepted' devices (likely will be a much shorter list) and  reject  .*  (all other devices) (as while-list)

(reading and parsing very long config files will get noticeable)

Comment 8 Jan Kurik 2017-12-06 11:54:16 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


Note You need to log in before you can comment on or make changes to this bug.