[
https://issues.apache.org/jira/browse/MYNEWT-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William San Filippo resolved MYNEWT-95.
---------------------------------------
Resolution: Fixed
This issue has been resolved. There were issues with how whitelisting was
enabled/disabled. The main issue being that both the interrupt (through the
scheduler) and the Link Layer task were enabling/disabling the whitelist and
race conditions existed. Now, when the scheduler runs or we start scanning we
either enable or disable scanning in the scheduler or with the scheduler
interrupt disabled. This way we are sure of the proper whitelist state for the
appropriate link layer state.
> BLE controller whitelisting enable/disable needs review
> -------------------------------------------------------
>
> Key: MYNEWT-95
> URL: https://issues.apache.org/jira/browse/MYNEWT-95
> Project: Mynewt
> Issue Type: Improvement
> Components: Nimble
> Affects Versions: v0_8_0_beta1
> Reporter: William San Filippo
> Assignee: William San Filippo
> Labels: controller
> Fix For: v0_8_0_rel
>
>
> The current implementation of BLE whitelist enabling/disabling needs review.
> It is possible that the Link Layer task and code running inside interrupt
> context is "conflicting", causing the Link Layer task to possibly disable the
> whitelist after being enabled by a different piece of the code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
