Fix ACTION=="add" udev rules

[bryan@linuxfromscratch.org]

The problem:

Per ​this post to linux-hotplug, the kernel will eventually start emitting a lot more ACTION=="change" uevents. So if udev rules have a match on ACTION=="add", they won't get applied to the changed device. This will break device naming, symlinks, and possibly other stuff.

What we need to do:

This should only involve investigating anywhere that we use ACTION=="add"; if it's only in the rule as a performance hack (to make it stop evaluating the rule when other stuff happens to the device), then change it to ACTION=="add|change". If the rule is really only supposed to be honored on device additions, then leave it alone.

(It would probably also be good to run the check commands that were given in that post, but until the upstream rules get fixed, they'll likely show a lot of false positives. So I haven't done that yet.)

This is (presumably) not a problem in any released kernel, and we're in a package freeze for 6.4, so I'm just adding this ticket as a reminder to check into this before 7.0. (Also I'll want to see where the discussion goes on linux-hotplug before committing anything.)

[Bryan Kadzban]

Fixed in r8771.