On 03/19/2010 10:24 AM, Kay Sievers wrote: > On Fri, Mar 19, 2010 at 10:06, Lars Ellenberg <lars.ellenberg@xxxxxxxxxx> wrote: >> Would introducing a KOBJ_READY_TO_BE_CONSUMED_BY_UDEV help? > > No, that's what "change" is for, and we already have these "change" > events for dm. Udev does not care if the device is ready or not, it > synchronizes /sys and /dev, and that works just fine with "change" > events. Udev (rules) do not not care if the device is ready? That's really news for me. So you are basically saying that dm ADD event is ok, and it is problem of udev rules that they react here on ADD event and run various scan over not-yet-ready device because it should wait for CHANGE? ok, then I am wasting time with fixing the dm ADD event. We have this already. Mea culpa. Sorry for spam then:-) Milan -- mbroz@xxxxxxxxxx -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
