-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix inifinte loop in esp32 RIO handling. #12736
Conversation
If the router is advertising a default prefix (::/0), the route handler is going into an infinite loop. Route information options can only have one prefix anyway, so the loop here is overkill and likely to introduce bad routes. Changing this to a simple check. Test: Configured radvd to advertise a default route, saw infinite loop on upstream, no problems with this code. Regular routes are being processed correctly.
PR #12736: Size comparison from 1f4024a to 84dda1e Decreases (2 builds for esp32)
Full report (32 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Fast track due to small size. This is more of a hotfix: this was demostratably causing infinite loops and that was fixed and tested. Any followup reviews will be done separately. For now, pushing the 'stop the ability to busyloop' out of the way. |
It's fine to just use |
Problem
If the router is advertising a default prefix (::/0), the route
handler is going into an infinite loop.
Route information options can only have one prefix anyway, so the
loop here is overkill and likely to introduce bad routes.
Change overview
Change for loop to a simple check that the size is sufficient.
Testing
Configured radvd to advertise a default route, saw infinite loop on upstream, no problems with this code. Regular routes are being processed correctly.