udev: also react to "move" (and "change") udev actions in our rules
NetworkManager handles "add" and "move" actions the same way, by tracking the "struct udev_device" instance. Still, this means that also for move events, we need the right attributes set. See-also: https://github.com/openshift/sriov-network-operator/issues/414
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
# To override or extend the rules place a file in /etc/udev/rules.d
|
||||
|
||||
SUBSYSTEM!="net", GOTO="nm_drivers_end"
|
||||
ACTION!="add|change", GOTO="nm_drivers_end"
|
||||
ACTION!="add|change|move", GOTO="nm_drivers_end"
|
||||
|
||||
# Determine ID_NET_DRIVER if there's no ID_NET_DRIVER or DRIVERS (old udev?)
|
||||
ENV{ID_NET_DRIVER}=="?*", GOTO="nm_drivers_end"
|
||||
|
@@ -2,7 +2,7 @@
|
||||
# To override or extend the rules place a file in /etc/udev/rules.d
|
||||
|
||||
SUBSYSTEM!="net", GOTO="nm_unmanaged_end"
|
||||
ACTION!="add|change", GOTO="nm_unmanaged_end"
|
||||
ACTION!="add|change|move", GOTO="nm_unmanaged_end"
|
||||
|
||||
# VirtualBox host networking. Out-of-tree driver that looks like an ordinary
|
||||
# Ethernet. No parent device (lives in /virtual/), no support for ethtool
|
||||
|
@@ -1,7 +1,7 @@
|
||||
# Do not modify this file, it will get overwritten on updates.
|
||||
# To override or extend the rules place a file in /etc/udev/rules.d
|
||||
|
||||
ACTION!="add", GOTO="nm_thunderbolt_end"
|
||||
ACTION!="add|change|move", GOTO="nm_thunderbolt_end"
|
||||
|
||||
# Load he thunderbolt-net driver if we a device of type thunderbolt_xdomain
|
||||
# is added.
|
||||
|
Reference in New Issue
Block a user