Peter Rajnoha c2981cf921 filters: use usable device filter and separate lvmetad filter chain so it's not reevaluated for any lvmetad response ... With this change, the filter chains used look like this now: A) When *lvmetad is not used*: - persistent filter -> regex filter -> sysfs filter -> global regex filter -> type filter -> usable device filter(FILTER_MODE_NO_LVMETAD) -> mpath component filter -> partitioned filter -> md component filter B) When *lvmetad is used* (two separate filter chains): - the lvmetad filter chain used when scanning devs for lvmetad update: sysfs filter -> global regex filter -> type filter -> usable device filter(FILTER_MODE_PRE_LVMETAD) -> mpath component filter -> partitioned filter -> md component filter - the filter chain used for lvmetad responses: persistent filter -> usable device filter(FILTER_MODE_POST_LVMETAD) -> regex filter		2014-09-30 13:22:11 +02:00
..
lvmcache.c	cleanup: just safely copy string	2014-07-04 12:31:17 +02:00
lvmcache.h	report: select: refactor: move str_list to libdm	2014-06-17 16:27:20 +02:00
lvmetad.c	filters: use usable device filter and separate lvmetad filter chain so it's not reevaluated for any lvmetad response	2014-09-30 13:22:11 +02:00
lvmetad.h	autoactivation: use VG read lock	2014-03-14 12:10:52 +01:00