Thomas Cuyckens
29df29f3e9
SendDeleteAddress() previously sent RTM_DELADDR via a raw send(), bypassing the pending netlink TX queue used by SendNetlinkMessage() for retrying on EAGAIN. If an RTM_NEWADDR for an address was still queued (e.g. because the kernel returned EAGAIN), a subsequent removal of that same address could be sent immediately and complete before the queued add, leaving the address present in the kernel after OpenThread had already removed it. Route deletes through SendNetlinkMessage() so they share the same FIFO queue as adds/replaces, preserving per-address ordering. FlushPendingRemoveAddresses() only retries an entry on OT_ERROR_BUSY (the TX queue is full); any other failure isn't retryable and the entry is dropped rather than spinning on it forever. It also stops at the first busy entry instead of trying later ones, so a later removal can't end up queued ahead of an earlier one once space frees up, and so it doesn't burn netlink sequence numbers or emit duplicate warnings for entries it can't make progress on anyway. platformNetifDeinit() now also resets sPendingRemoveAddrsCount alongside clearing the TX queue, so failed/busy entries don't persist across a deinit/reinit cycle. platformNetifProcess() now flushes pending removals after draining the TX queue via ProcessPendingNetlinkTx() instead of before, so a flush gets the benefit of any space ProcessPendingNetlinkTx() just freed instead of failing against a queue that's still full from before select() was called.
What is OpenThread?
OpenThread released by Google is... 
...an open-source implementation of the Thread networking protocol. Google Nest has released OpenThread to make the technology used in Nest products more broadly available to developers to accelerate the development of products for the connected home.
...OS and platform agnostic, with a narrow platform abstraction layer and a small memory footprint, making it highly portable. It supports both system-on-chip (SoC) and network co-processor (NCP) designs.
...a Thread Certified Component, implementing all features defined in the Thread 1.4.0 specification, including all Thread networking layers (IPv6, 6LoWPAN, IEEE 802.15.4 with MAC security, Mesh Link Establishment, Mesh Routing) and device roles, as well as Border Router support.
More information about Thread can be found at threadgroup.org. Thread is a registered trademark of the Thread Group, Inc.
Who supports OpenThread?
Getting started
All end-user documentation and guides are located at openthread.io. If you're looking to do things like...
- Learn more about OpenThread features and enhancements
- Use OpenThread in your products
- Learn how to build and configure a Thread network
- Port OpenThread to a new platform
- Build an application on top of OpenThread
- Certify a product using OpenThread
...then openthread.io is the place for you.
Note: For users in China, end-user documentation is available at openthread.google.cn.
If you're interested in contributing to OpenThread, read on.
Contributing
We would love for you to contribute to OpenThread and help make it even better than it is today! See our Contributing Guidelines for more information.
Contributors are required to abide by our Code of Conduct and Coding Conventions and Style Guide.
License
OpenThread is released under the BSD 3-Clause license. See the LICENSE file for more information.
Please only use the OpenThread name and marks when accurately referencing this software distribution. Do not use the marks in a way that suggests you are endorsed by or otherwise affiliated with Nest, Google, or The Thread Group.
Need help?
OpenThread support is available on GitHub:
- Bugs and feature requests — submit to the Issue Tracker
- Community Discussion - ask questions, share ideas, and engage with other community members