mirror of
git://sourceware.org/git/lvm2.git
synced 2025-03-10 16:58:47 +03:00
cac49725c9
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 756bcabbfe297688ba240a880bc2b55265ad33f0. We already had a similar problem with MD devices which was fixed by 2ac217d408470dcecb69b83d9cbf7a254747fa5b (but that one was only an intra-release fix).