Peter Rajnoha 80ac8f37d6 filters: fix incorrect filter indexing in composite filter array ...

Caused by recent changes - a7be3b12dfe7388d1648595e6cc4c7a1379bb8a7.
If global filter was not defined, then part of the code
creating composite filter (the cmd->lvmetad_filter) incorrectly
increased index value even if this global filter was not created
as part of the composite filter. This caused a gap with "NULL"
value in the composite filter array which ended up with the rest
of the filters after the gap to be ignored and also it caused a mem
leak when destroying the composite filter.

2014-09-11 09:30:03 +02:00

..

toolcontext.c

filters: fix incorrect filter indexing in composite filter array

2014-09-11 09:30:03 +02:00

toolcontext.h

conf: add report/list_item_separator lvm.conf option

2014-07-10 16:18:45 +02:00