[nrf fromtree] Bluetooth: Host: Fix issue where uninitialized value w… #2109
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.
…as used
This change makes sure that when a call to
bt_id_set_scan_own_addr
is sucessful, i.e., the return value is 0, theown_addr_type
will be set by thebt_id_set_scan_own_addr
.Not setting the
own_addr_type
in a successful call tobt_id_set_scan_own_addr
causes, for example,the
start_le_scan_ext
method inscan.c
to use an uninitializedown_addr_type
.Eventually this results in an unexpected failure further down in
start_le_scan_ext
, when sending HCI command to controller with an uninitializedown_addr_type
.Signed-off-by: Erik Sandgren [email protected]
(cherry picked from commit 5f59b35)