On Wed, Apr 8, 2009 at 05:04, Peter Rajnoha <prajnoha@xxxxxxxxxx> wrote: > this is a kernel side patch that adds support for cookie variables. > A cookie is a random unsigned 32 bit value generated in userspace > and passed into the DM through ioctl (reusing the event_nr field to > avoid the change in the interface). These values are sent back in > CHANGE and REMOVE uevents. This way we can easily pair a process > waiting for udev's rule completion and the udev event itself. That sounds useful. I always thought we would return the driver core generated seqnum with the ioctl, so you could watch the udev event queue to see the events being handled. But if you are going to listen to the udev events, the cookie sounds like a nice solution. > Also, > we can use the cookie value to group the actions and related uevents > together, so we know which uevents belong to actions done on one > DM tree. If you would use the same cookie for several actions, how do you track, that udev has finished the work when you expect an arbitrary number of events with the same cookie? Thanks, Kay -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
