diff options
author | Yu Watanabe <watanabe.yu+github@gmail.com> | 2021-05-24 07:53:05 +0200 |
---|---|---|
committer | Yu Watanabe <watanabe.yu+github@gmail.com> | 2021-06-07 23:33:27 +0200 |
commit | 793117b3fd4c2dbbe9ddd9cfb7795a623379e5b6 (patch) | |
tree | 8c7bcd352304db6c9b4fc15fe4c9fb9ccbe355f8 /src/network/networkd-link.c | |
parent | network: introduces link_drop_ipv6ll_addresses() (diff) | |
download | systemd-793117b3fd4c2dbbe9ddd9cfb7795a623379e5b6.tar.xz systemd-793117b3fd4c2dbbe9ddd9cfb7795a623379e5b6.zip |
network: drop meaningless condition about setting MTU
The condition does not fix infinite loop of interface reset, as the
interface is reset after netlink reply is received, thus setting_mtu is
false.
See also #18738.
Diffstat (limited to '')
-rw-r--r-- | src/network/networkd-link.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/src/network/networkd-link.c b/src/network/networkd-link.c index 74a73419d6..13faa26b2a 100644 --- a/src/network/networkd-link.c +++ b/src/network/networkd-link.c @@ -2815,12 +2815,6 @@ static int link_carrier_lost(Link *link) { /* let's shortcut things for CAN which doesn't need most of what's done below. */ return link_handle_bound_by_list(link); - /* Some devices reset itself while setting the MTU. This causes the DHCP client fall into a loop. - * setting_mtu keep track whether the device got reset because of setting MTU and does not drop the - * configuration and stop the clients as well. */ - if (link->setting_mtu) - return 0; - r = link_stop_engines(link, false); if (r < 0) { link_enter_failed(link); |