Revert "udev: run link_update() with increased retry count in second invocation"
authorMichal Sekletar <msekleta@redhat.com>
Mon, 17 May 2021 13:49:08 +0000 (15:49 +0200)
committerThe Plumber <50238977+systemd-rhel-bot@users.noreply.github.com>
Wed, 19 May 2021 08:20:23 +0000 (10:20 +0200)
This reverts commit 1f3165bda13c8572c8c31d23c998835c4e2ad8f3.

Related: #1942299

src/udev/udev-event.c

index eaec05523bb3e00bef4d5ce6f33883bbcd1c439c..9004634f65d26a8f577fb2bd83202dbeb76c08b0 100644 (file)
@@ -934,13 +934,14 @@ void udev_event_execute_rules(struct udev_event *event,
                 /* (re)write database file */
                 udev_device_tag_index(dev, event->dev_db, true);
                 udev_device_update_db(dev);
-                udev_device_set_is_initialized(dev);
 
                 /* Yes, we run update_devnode() twice, because in the first invocation, that is before update of udev database,
                  * it could happen that two contenders are replacing each other's symlink. Hence we run it again to make sure
                  * symlinks point to devices that claim them with the highest priority. */
                 update_devnode(event);
 
+                udev_device_set_is_initialized(dev);
+
                 event->dev_db = udev_device_unref(event->dev_db);
         }
 }