device: ensure not rescheduling IP config changed on initial capture
update_ip4_config() and update_ip6_config() are called from nm_device_capture_initial_config(). At that point, we don't expect any activation-source scheduled, thus the "if" should not not be hit anyway. So, this patch should actually make no difference, but it seems clearer to me. Also, because it would be a bug to re-schedule the idle handler that is already pending, but from inspecting nm_device_capture_initial_config() it is not immediately clear that this cannot be the case.
This commit is contained in:
@@ -8923,7 +8923,8 @@ update_ip4_config (NMDevice *self, gboolean initial)
|
|||||||
* it changing IP configurations before they are applied. Postpone the
|
* it changing IP configurations before they are applied. Postpone the
|
||||||
* update in such case.
|
* update in such case.
|
||||||
*/
|
*/
|
||||||
if (activation_source_is_scheduled (self,
|
if ( !initial
|
||||||
|
&& activation_source_is_scheduled (self,
|
||||||
activate_stage5_ip4_config_commit,
|
activate_stage5_ip4_config_commit,
|
||||||
AF_INET)) {
|
AF_INET)) {
|
||||||
priv->queued_ip4_config_id = g_idle_add (queued_ip4_config_change, self);
|
priv->queued_ip4_config_id = g_idle_add (queued_ip4_config_change, self);
|
||||||
@@ -9012,7 +9013,8 @@ update_ip6_config (NMDevice *self, gboolean initial)
|
|||||||
* it changing IP configurations before they are applied. Postpone the
|
* it changing IP configurations before they are applied. Postpone the
|
||||||
* update in such case.
|
* update in such case.
|
||||||
*/
|
*/
|
||||||
if (activation_source_is_scheduled (self,
|
if ( !initial
|
||||||
|
&& activation_source_is_scheduled (self,
|
||||||
activate_stage5_ip6_config_commit,
|
activate_stage5_ip6_config_commit,
|
||||||
AF_INET6)) {
|
AF_INET6)) {
|
||||||
priv->queued_ip6_config_id = g_idle_add (queued_ip6_config_change, self);
|
priv->queued_ip6_config_id = g_idle_add (queued_ip6_config_change, self);
|
||||||
|
Reference in New Issue
Block a user