Never call udevadm trigger!
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dkms (Ubuntu) |
Fix Released
|
Critical
|
Mario Limonciello | ||
Intrepid |
Fix Released
|
Critical
|
Unassigned |
Bug Description
IMPACT:
DKMS must *NOT* call udevadm trigger.
This will have utterly dire consequences for the installed machine.
Minor bugs will be things like Network Manager and GNOME Power Manager reporting multiple copies of network cards, or batteries.
Major bugs will be apparent corruption of mounted filesystems (e.g. "/usr: data error") until a reboot.
And critical bugs include the entire /dev changing to root:root/660 on upgrade.
ADDRESSING BUG:
This has been fixed in git HEAD, as well as in jaunty.
TEST CASE:
On a system that is using DKMS, try to remove an installed module and reinstall it. When DKMS is using udevadm trigger, you will see your network device duplicated in Network Manager. You will also disconnect and reconnect from the network.
For a specified MODULE and VERSION, the following should be a good test case.
dkms remove -m MODULE -v VERSION --all
/etc/init.
REGRESSION POTENTIAL:
Anyone that was relying on this behavior of DKMS will have to manually modprobe the module that was just built themselves or in a postinstall. Also, a reboot would resolve this behavior.
Changed in dkms: | |
importance: | Undecided → Critical |
status: | New → Confirmed |
Changed in dkms: | |
importance: | Undecided → Critical |
status: | New → Confirmed |
description: | updated |
description: | updated |
http:// linux.dell. com/git/ ?p=dkms. git;a=commit; h=72c7412fe6125 d635e40a7eead6f 040acab71001