Peter Rajnoha cac49725c9 udev: fix lvmetad rules to not ignore loop device configuration ... If loop device is first configured on systems where /dev/loop-control is used to dynamically create the loop device itself, there's an ADD+CHANGE even generated. But next time the existing /dev/loop[0-9]* is reused, there's only a CHANGE event since the device representing it is already present in kernel (so no ADD event in this case). We can't ignore this CHANGE event for loop devices! This is a regression caused by 756bcabbfe. We already had a similar problem with MD devices which was fixed by 2ac217d408 (but that one was only an intra-release fix).		2013-08-16 15:45:00 +02:00
..
10-dm.rules.in	udev: add a few comments about variables used to recognize events	2013-05-03 11:01:57 +02:00
11-dm-lvm.rules.in	udev: udev rules cleanup	2012-06-27 12:11:56 +02:00
12-dm-permissions.rules	add copyright lines	2009-10-26 22:42:07 +00:00
13-dm-disk.rules.in	Call built-in blkid conditionaly (udev version >= 176), call standard blkid	2012-02-20 19:38:40 +00:00
69-dm-lvm-metad.rules.in	udev: fix lvmetad rules to not ignore loop device configuration	2013-08-16 15:45:00 +02:00
95-dm-notify.rules.in	udev: udev rules cleanup	2012-06-27 12:11:56 +02:00
Makefile.in	udev: udev rules cleanup	2012-06-27 12:11:56 +02:00