TJ if that's the case then this is probably a flaw of the entire block IO system design.
In my mind, the ideal solution would be to have an abstraction which eventually reduces to a list of raw devices and block-ranges of action per device. When a watch or event occurs it would only be within that range. Multiple virtual devices might match against different ranges of raw block devices. If the device, block-range, and some type of timestamp of the event were combined a unique key would be formed. Generating events only from the raw device and reflecting them up to directly linked virtual block abstractions would place an implicit limit in the data-structures and execution path. -- udev repeatedly generates "change" events for the same block device(s) https://bugs.launchpad.net/bugs/332270 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
