From: Archie Pusaka <apusaka@xxxxxxxxxxxx> After the patches which limit the attempts of doing remote name resolving, there's an issue which prevents BlueZ to RNR new devices for 5 minutes after reboot. It's caused by failed_time is init to 0, and is then treated as the timestamp when the device failed RNR. However, actually there is no failure yet. This patch fixes it by always allowing RNR when failed_time = 0. --- Changes in v2: * Separate the one big if into multiple smaller ifs for clarity src/device.c | 22 +++++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git a/src/device.c b/src/device.c index f2447c478e..6d29eb8966 100644 --- a/src/device.c +++ b/src/device.c @@ -4487,12 +4487,24 @@ bool device_is_name_resolve_allowed(struct btd_device *device) clock_gettime(CLOCK_MONOTONIC, &now); - /* If now < failed_time, it means the clock has somehow turned back, - * possibly because of system restart. Allow name request in this case. + /* failed_time is empty (0), meaning no prior failure. */ + if (device->name_resolve_failed_time == 0) + return true; + + /* now < failed_time, meaning the clock has somehow turned back, + * possibly because of system restart. Allow just to be safe. + */ + if (now.tv_sec < device->name_resolve_failed_time) + return true; + + /* now >= failed_time + name_request_retry_delay, meaning the + * period of not sending name request is over. */ - return now.tv_sec < device->name_resolve_failed_time || - now.tv_sec >= device->name_resolve_failed_time + - btd_opts.name_request_retry_delay; + if (now.tv_sec >= device->name_resolve_failed_time + + btd_opts.name_request_retry_delay) + return true; + + return false; } void device_name_resolve_fail(struct btd_device *device) -- 2.34.1.575.g55b058a8bb-goog
