michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Bluetooth: Settings: Fix generated identity not persistently stored.

Browse source 
Fix an issue where the generated identity was not permanently stored.
This resulted in being unable to reconnect after bonding when using
privacy, since a new local IRK was generated on reboot.

When settings is enabled the application is responsible for loading
identities and possible creating its own identities.
When settings_load is called and no identities has been created or found
in persistent storage a new identity will be created.
Since bt init has not been finalized bt_id_create will not make a call
to bt_settings_save_id. So we need to make sure that this identity will
be stored.

Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
This commit is contained in:
Joakim Andersson 2019-07-30 16:55:47 +02:00 • committed by Carles Cufí
commit 2b84c726c8
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
subsys/bluetooth/host/settings.c
View file

@ -217,6 +217,12 @@ static int commit(void)
} }
} }
/* Make sure that the identities created by bt_id_create after
* bt_enable is saved to persistent storage. */
if (!atomic_test_bit(bt_dev.flags, BT_DEV_PRESET_ID)) {
bt_settings_save_id();
}
if (!atomic_test_bit(bt_dev.flags, BT_DEV_READY)) { if (!atomic_test_bit(bt_dev.flags, BT_DEV_READY)) {
bt_finalize_init(); bt_finalize_init();
} }