Lennart Poettering
a7fdc6cbd3
Let's open the device node to modify with O_PATH, and then adjust it only after verifying everything is in order. This fixes a race where the a device appears, disappears and quickly reappers, while we are still running the rules for the first appearance: when going by path we'd possibly adjust half of the old and half of the new node. By O_PATH we can pin the node while we operate on it, thus removing the race. Previously, we'd do a superficial racey check if the device node changed undearneath us, and would propagate EEXIST in that case, failing the rule set. With this change we'll instead gracefully handle this, exactly like in the pre-existing case when the device node disappeared in the meantime.
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 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.