Fix hostapd's place in systemd dependency tree. #45464
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Here is the dependency graph that I get with this PR. Notice that br0-netdev.service depends on network-link-wlp4s0.service which depends on hostapd.service which depends on sys-subsystem-net-devices-wlp4s0.device. You can generate this graph yourself with: |
GrahamcOfBorg
added
6.topic: nixos
Mic92
reviewed
Aug 22, 2018
|
|
||
| after = [ "${cfg.interface}-cfg.service" "nat.service" "bind.service" "dhcpd.service" "sys-subsystem-net-devices-${cfg.interface}.device" ]; | ||
| after = [ "sys-subsystem-net-devices-${cfg.interface}.device" ]; | ||
| requiredBy = [ "network-link-${cfg.interface}.service" ]; |
There was a problem hiding this comment.
Maybe it should also add BindsTo=sys-subsystem-net-devices-wlan0.device?
There was a problem hiding this comment.
Arch does After=network.target, but I guess they just cannot add more specific requirements because they don't know which interface will be used.
There was a problem hiding this comment.
Yes, BindsTo seems appropriate. I'll switch after to BindsTo as BindsTo is already implies the effects of after.
after=network.target is not correct, as this potentially would hoist hostapd to the top of the dependency tree and causes the race to reappear. To get a visual idea of that, please look at the pdf attached in my PR comment. Also after=network.target gives a cyclic after chain of hostapd->network->br0-netdev->network-link-wl4s0->hostapd. Somebody in #16090 said they had the same bridge race with Arch. Maybe that's the reason. I'll ping this PR to them.
clefru
force-pushed
the
hostapd-dep-fix-on-master
branch
2 times, most recently
from
e68f914
to
b8d1638
Compare
|
@clefru your patch does not work here probosed solutionmerge our patches as this: i've tried with these configs seem to use a combination of
with only your patchpatch: outcome: journalctl -u hostapd then it works with our patches combinedboot log: journalctl -u hostapd |
* nat/bind/dhcp.service:
Remove. Those services have nothing to do with a link-level service.
* sys-subsystem-net-devices-${if}.device:
Add as BindsTo dependency as this will make hostapd stop when the
device is unplugged.
* network-link-${if}.service:
Add hostapd as dependency for this service via requiredBy clause,
so that the network link is only considered to be established
only after hostapd has started.
* network.target:
Remove this from wantedBy clause as this is already implied from
dependencies stacked above hostapd. And if it's not implied than
starting hostapd is not required for this particular network
configuration.
clefru
force-pushed
the
hostapd-dep-fix-on-master
branch
from
b8d1638
to
4b14f01
Compare
|
@qknight I have updated the PR as you suggested (retaining the after clause). Thanks for you analysis. (Also I reread the systemd.unit manpage, and my assertation above that "BindsTo" effects subsume those of "after" is wrong, hence it's still needed) |
|
@clefru ok, when you think the PR is ready i evaluate it once more, then we merge |
|
@qknight Please re-evaluate the PR as I updated it with your suggestions. Thank you! |
clefru
added a commit
to clefru/nixpkgs
that referenced
this pull request
Oct 17, 2018
* nat/bind/dhcp.service:
Remove. Those services have nothing to do with a link-level service.
* sys-subsystem-net-devices-${if}.device:
Add as BindsTo dependency as this will make hostapd stop when the
device is unplugged.
* network-link-${if}.service:
Add hostapd as dependency for this service via requiredBy clause,
so that the network link is only considered to be established
only after hostapd has started.
* network.target:
Remove this from wantedBy clause as this is already implied from
dependencies stacked above hostapd. And if it's not implied than
starting hostapd is not required for this particular network
configuration.
(cherry picked from commit 725fcde)
Mic92
added a commit
that referenced
this pull request
Oct 17, 2018
Fix hostapd's place in systemd dependency tree. (#45464)
|
This broke hostapd when using systemd-networkd, because |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
after clause:
requiredBy clause:
wantedBy clause:
stacked above hostapd. And if it's not implied than starting hostapd is not required
for this particular network configuration.
Motivation for this change
bridge setup races with hostapd, and if it wins, the bridge fails to start, see: #16090
Things done
sandboxinnix.confon non-NixOS)nix-shell -p nox --run "nox-review wip"./result/bin/)nix path-info -Sbefore and after)