Support for reboot 0 broken

[fabled]

man dhcpcd.conf says:

reboot seconds
[...]
A setting of 0 seconds causes dhcpcd.conf to skip the reboot phase and go straight into DISCOVER.

Using this configuration now results in indefinite busy loop with the following log output:

wlan0: probing for an IPv4LL address
wlan0: offered 192.168.88.10 from 192.168.88.1
wlan0: failed to request the lease
wlan0: soliciting a DHCP lease
wlan0: probing for an IPv4LL address
wlan0: offered 192.168.88.10 from 192.168.88.1
wlan0: failed to request the lease
wlan0: soliciting a DHCP lease
wlan0: probing for an IPv4LL address
wlan0: offered 192.168.88.10 from 192.168.88.1
wlan0: failed to request the lease
wlan0: soliciting a DHCP lease
wlan0: probing for an IPv4LL address
wlan0: offered 192.168.88.10 from 192.168.88.1
wlan0: failed to request the lease
wlan0: soliciting a DHCP lease
wlan0: probing for an IPv4LL address
wlan0: offered 192.168.88.10 from 192.168.88.1
wlan0: failed to request the lease

Git bisect says this got broken with commit d408e74.

[fabled]

Sounds the logic is wrong. Reboot should likely trigger once, but seems the reboot timer gets rescheduled for every request. Would probably be good to just handle reboot 0 immediately instead of via scheduling a timeout.