-
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
Add some better memory safety in discovery controller code. #8281
Merged
bzbarsky-apple
merged 1 commit into
project-chip:master
from
bzbarsky-apple:better-typesafety-discovery
Jul 12, 2021
Merged
Add some better memory safety in discovery controller code. #8281
bzbarsky-apple
merged 1 commit into
project-chip:master
from
bzbarsky-apple:better-typesafety-discovery
Jul 12, 2021
Conversation
This file contains 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
pullapprove
bot
requested review from
chrisdecenzo,
jelderton,
jmartinez-silabs,
LuDuda,
mspang,
sagar-apple,
saurabhst and
woody-apple
July 10, 2021 08:57
Instead of assuming that subclasses give us a buffer of size at least CHIP_DEVICE_CONFIG_MAX_DISCOVERED_NODES, just enforce that via the type system. Also switch to ranged for loops over the resulting buffers. The changes to Span.h are for two reasons: 1) To support ranged for over a FixedSpan. 2) To disallow constructing a FixedSpan from a buffer known to be too small.
bzbarsky-apple
force-pushed
the
better-typesafety-discovery
branch
from
July 10, 2021 19:11
e739573
to
553ed75
Compare
Size increase report for "esp32-example-build" from 0e19e0d
Full report output
|
andy31415
approved these changes
Jul 12, 2021
saurabhst
approved these changes
Jul 12, 2021
jmartinez-silabs
approved these changes
Jul 12, 2021
nikita-s-wrk
pushed a commit
to nikita-s-wrk/connectedhomeip
that referenced
this pull request
Sep 23, 2021
…chip#8281) Instead of assuming that subclasses give us a buffer of size at least CHIP_DEVICE_CONFIG_MAX_DISCOVERED_NODES, just enforce that via the type system. Also switch to ranged for loops over the resulting buffers. The changes to Span.h are for two reasons: 1) To support ranged for over a FixedSpan. 2) To disallow constructing a FixedSpan from a buffer known to be too small.
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.
Instead of assuming that subclasses give us a buffer of size at least CHIP_DEVICE_CONFIG_MAX_DISCOVERED_NODES, just enforce that via the type system.
Also switch to ranged for loops over the resulting buffers.
The changes to Span.h are for two reasons:
Problem
Code makes assumptions about buffer sizes that are not enforced.
Change overview
Enforce assumptions through type system.
Testing
Compiles and passes CI. Should be no behavior changes.