SW-281365 fix dhcpcd route overflow recovery#18
Merged
aminescu-dn merged 3 commits intoJul 9, 2026
Conversation
colaru-dn
approved these changes
Jul 6, 2026
aminescu-dn
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Route socket overflow currently forces an immediate full interface-state rebuild every time the kernel reports
ENOBUFS. Under sustained route churn this makesdhcpcdspend most of its time relearning the same state, which amplifies CPU and memory pressure in the inband container.This change keeps the urgent part of the handler immediate: drain the route socket so the event loop can continue. The expensive interface rediscovery is scheduled once and coalesced while another recovery is already pending, limiting repeated full rebuilds during an overflow storm.
If scheduling the delayed recovery fails,
dhcpcdfalls back to the previous synchronous recovery path.