summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFernando Fernandez Mancera <ffmancera@riseup.net>2022-02-10 09:53:20 +0100
committerFernando Fernandez Mancera <ffmancera@riseup.net>2022-02-10 10:36:31 +0100
commit7f4604f31e82522457704e0dc1826126a7664565 (patch)
treea60f9a4f46600d2b000ea9dfbc3d423be2ef79f7
parentd9fbfad9f4f4dffcf2b244f6b28bbb67f035faec (diff)
nm-l3cfg: fix check on timestamp for assuming probing is goodff/dad_timeout
https://bugzilla.redhat.com/show_bug.cgi?id=2028751 Fixes: db0d84f13a (“l3cfg: fix handling "instance-reset" ACD event”)
-rw-r--r--src/core/nm-l3cfg.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/core/nm-l3cfg.c b/src/core/nm-l3cfg.c
index e7aee79a04..9258decf07 100644
--- a/src/core/nm-l3cfg.c
+++ b/src/core/nm-l3cfg.c
@@ -2469,9 +2469,9 @@ handle_init:
nm_utils_get_monotonic_timestamp_msec_cached(p_now_msec);
if (acd_data->info.state == NM_L3_ACD_ADDR_STATE_PROBING) {
- if (acd_data->probing_timestamp_msec + ACD_WAIT_PROBING_EXTRA_TIME_MSEC
- + ACD_WAIT_PROBING_EXTRA_TIME2_MSEC
- >= (*p_now_msec)) {
+ if ((*p_now_msec) > acd_data->probing_timestamp_msec
+ + ACD_WAIT_PROBING_EXTRA_TIME_MSEC
+ + ACD_WAIT_PROBING_EXTRA_TIME2_MSEC) {
/* hm. We failed to create a new probe too long. Something is really wrong
* internally, but let's ignore the issue and assume the address is good. What
* else would we do? Assume the address is USED? */