Milan Broz wrote: > On 03/19/2010 11:16 AM, Kay Sievers wrote: > >> There are several subsystems that depend on updating everything with >> "change" events when device configurations change. There is nothing >> inherently wrong with this approach, as long as subsystems send the >> proper "change" events and don't try to hide anything they have >> registered. > > ok, this is perfectly fine with dm devices, CHANGE announces all > changes. Just I am not sure if all consumers of events (and separate > rules authors) know about that, I saw so many problems with > failing something when wrongly reacting to ADD event... > > Also it means that after ADD the by-uuid* and similar symlinks > cannot be yet trusted - if the UUID is read from device and device > is not yet ready. > Correct. We try to take care of that one by a) not running something like 'vol_id' for 'ADD' events on dm devices and b) really making sure the dm device can be read from when receiving CHANGE event. > Well. And what should happen if anyone generate > artificial CHANGE event before the real first CHANGE event comes from > subsystem? (yes, I am looking at you, OPTIONS+="watch" thing for example) > You have to check the device anyway. 'CHANGE' literally just means that, ie something has changed with the device state. We used to have 'ONLINE' and 'OFFLINE' events for block devices, but that got modified to the more generic 'CHANGE' event. There is _no_ indication what has changed with the device state; any program etc must check for itself if the device is in a usable state. (Normally there won't even be any additional environment variables with a 'CHANGE' event, so one has to look in sysfs anyway to find out what has changed). > According to above, rules must be written such way that every ADD/CHANGE > event must expect that device is not ready, so it can create only > partial info in udev, is it correct? Correct. > (this is of course no problem if the rules are the same for both cases) > Well, yes and no. We (read: SUSE) are trying to make sure to _not_ run any programs likely to read data from the disk when receiving 'ADD' events from these devices. You might get lucky here when the 'ADD' event is in fact a fake as it was triggered externally, but this is not something I'd bank on. (And if someone is faking 'ADD' events he can as well do it properly and fake the corresponding 'CHANGE' events, too) HTH. Cheers, Hannes -- Dr. Hannes Reinecke zSeries & Storage hare@xxxxxxx +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
