Yu Watanabe
5d354e525a
Previously, if a block device is locked by another process, then the corresponding worker skip to process the corresponding event, and does not broadcast the uevent to libudev listners. This causes several issues: - During a period of a device being locked by a process, if a user trigger an event with `udevadm trigger --settle`, then it never returned. - When there is a delay between close and unlock in a process, then the synthesized events triggered by inotify may not be processed. This can happens easily by wrapping mkfs with flock. This causes severe issues e.g. new devlinks are not created, or old devlinks are not removed. This commit makes events are requeued with a tiny delay when the corresponding block devices are locked by other processes. With this way, the triggered uevent may be delayed but is always processed by udevd. Hence, the above issues can be solved. Also, it is not necessary to watch a block device unconditionally when it is already locked. Hence, the logic is dropped.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.