Improve handling of ENOBUFS by not running in a tight loop forever.
authorflorian <florian@openbsd.org>
Mon, 11 Sep 2023 06:00:23 +0000 (06:00 +0000)
committerflorian <florian@openbsd.org>
Mon, 11 Sep 2023 06:00:23 +0000 (06:00 +0000)
commitafda2c0320d498fdab6d54743c6adaa7208e5ff6
tree04ca65b0d61c1ffb636f0f6a4503ed5ceb307770
parentc824b3ec91bf01f0e5cb68f23fc525c95b0d5349
Improve handling of ENOBUFS by not running in a tight loop forever.

This cherry-picks upstream git commit
0ee44ef384593ed0382d1ce6048d5a9c9440b45c.

Issue reported by landry@, which could be traced back to a buggy WiFi
driver that would constantly return ENOBUFS. This in turn lead
unwind(8) enter a tight loop through poll / sendto without making any
progress and burning 100% cpu.

OK sthen
sbin/unwind/resolver.c
usr.sbin/unbound/doc/Changelog
usr.sbin/unbound/util/netevent.c