[FS#1903] Hotplug event triggered too early

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1903 - Hotplug event triggered too early
User who did this - Luiz Angelo Daros de Luca (luizluca)

----------
Could plug might be required for loading modules (extroot?) as well as loaded modules are might be needed to correctly process cold plug events. If udevtrigger can be executed twice without a bad side effect, I would call it again after all modules are loaded and call it a day. OpenWrt used to do that in the past.

Normally a plug event emits a bunch of udev events (usb, usbmisc, ...). Some of them happen after/if a module is loaded, even if that happens seconds after the first events for that device. If the sequence of udev events is the same for a hot and could plug, it is working as expected no matter the delay between them. If not, it is a bug.

In this specific case, the created symlink might be trigged by another udev event when the module was loaded. Maybe your hotplug script might need to be trigged by that event and not the usb event you are using. The same would happen if the module package was installed with the usb device plugged and hotplug script was already in place (after an upgrade, for example)
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1903#comment9149

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.