| Age | Commit message (Collapse) | Author |
|---|
|
When we read the 'uevent' file we need to make sure, that we do not
read the relative DEVNAME= path provided by the kernel and overwrite
the absolute path udev expects here.
|
|
|
|
https://launchpad.net/bugs/901513
|
|
https://launchpad.net/bugs/902332
|
|
https://launchpad.net/bugs/902798
|
|
https://bugs.launchpad.net/bugs/914838
|
|
Some broken kernel drivers load firmware synchronously in the module init
path and block modprobe until the firmware request is fulfilled.
The modprobe-generated firmware request is a direct child device of the
device which caused modprobe to run. Child device event are blocked until
the parent device is handled. This dead-locks until the kernel firmware
loading timeout of 60 seconds is reached.
The hanging modprobe event should now time-out and allow the firmware
event to run before the 60 second kernel timeout.
|
|
<ridikulus_rat> 60-persistent-storage.rules gpt by-partlabel/by-partuuid
symlinks not created in udev-177 util-linux-2.20.1 kmod-3 in Archlinux x86_64.
<falconindy> ridikulus_rat: fix the rule, or fix the blkid builtin ;)
<kay> oh, i missed the ID_ stuff? :)
|
|
- Include exported package information
- Include C include information
- g_udev_device_get_parent & g_udev_device_get_parent_with_subsystem
transfer ownership of their return values
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
