From 0064401e35674093aaa2f4d05c30cbc38ec01fb2 Mon Sep 17 00:00:00 2001 From: Beniamino Galvani Date: Thu, 5 Dec 2019 15:39:56 +0100 Subject: [PATCH] device: always allow reapply of MTU from wired setting Many device types take the MTU value from the wired setting; usually they don't implement the can_reapply_change() method and so the MTU can't be changed with the Reapply() API. Instead of implementing the method for all such devices to support the same property (adding a lot of duplicated code), add a check in NMDevice to allow the reapply of MTU when we recognize that the device uses the MTU from the wired setting. Device types can still decide to implement can_reapply_change() and support whatever properties they want, even from the wired setting. (cherry picked from commit 9339d3310e48e14f58428ec923ed9c653df1693b) (cherry picked from commit 1191eba15aee386c8f01dc931da5925712bdbaf8) --- src/devices/nm-device.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/devices/nm-device.c b/src/devices/nm-device.c index 81913ca9f1..b2295ef1ae 100644 --- a/src/devices/nm-device.c +++ b/src/devices/nm-device.c @@ -11497,6 +11497,14 @@ can_reapply_change (NMDevice *self, NM_SETTING_IP4_CONFIG_SETTING_NAME, NM_SETTING_IP6_CONFIG_SETTING_NAME)) { return TRUE; + } else if ( nm_streq (setting_name, NM_SETTING_WIRED_SETTING_NAME) + && NM_IN_SET (NM_DEVICE_GET_CLASS (self)->get_configured_mtu, + nm_device_get_configured_mtu_wired_parent, + nm_device_get_configured_mtu_for_wired)) { + return nm_device_hash_check_invalid_keys (diffs, + NM_SETTING_WIRED_SETTING_NAME, + error, + NM_SETTING_WIRED_MTU); } else { g_set_error (error, NM_DEVICE_ERROR,