lwip: enable LWIP_SO_RCVTIMEO if sock layer is used #17779
Merged
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.
Contribution description
It is extremely counter-intuitive that LWIP will by default ignore timeouts unless
LWIP_SO_RCVTIMEO
is set.When using the sock API, the application should not have to care what backend is used and timeouts are part of the sock API - so always enable timeouts in LWIP when the sock API is in use.
Testing procedure
lwip tests should still pass without manually setting
LWIP_SO_RCVTIMEO
tests/lwip_sock_udp
Issues/PRs references