2b513af2c3
For example a race in managing tcb->sigprocmask may cause signal not being delivered at all. The mechanism is as follows: 1. cpu 1: nxsig_deliver adds the signal to the sigprocmask for the duration of signal delivery 2. cpu 2: new signal (same signo) is dispatched in nxsig_tcbdispatch 3. cpu 2: nxsig_tcbdispatch detects that signal is masked 4. cpu 2: nxsig_tcbdispatch leaves critical section before calling nxsig_add_pendigsignal 5. cpu 1: nxsig_deliver finishes. The "nxsig_unmask_pendingsignal" is called in the end but does nothing 6. cpu 2: nxsig_tcbdispatch continues and adds the pending signal In the end, the logic in the end of nxsig_deliver, which tries to handle signals added to the pending queue during the signal action delivery (step 5) failed, and the pending signal was not delivered. Fix this by just keeping the critical section for during the whole duration of nxsig_tcbdispatch, and move things which can't be executed from within critical section outside. Signed-off-by: Jukka Laitinen <jukka.laitinen@tii.ae> |
||
|---|---|---|
| .github | ||
| arch | ||
| audio | ||
| binfmt | ||
| boards | ||
| cmake | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| dummy | ||
| fs | ||
| graphics | ||
| include | ||
| libs | ||
| mm | ||
| net | ||
| openamp | ||
| pass1 | ||
| sched | ||
| syscall | ||
| tools | ||
| video | ||
| wireless | ||
| .asf.yaml | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| INVIOLABLES.md | ||
| Kconfig | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| ReleaseNotes | ||
Apache NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).
For brevity, many parts of the documentation will refer to Apache NuttX as simply NuttX.
Getting Started
First time on NuttX? Read the Getting Started guide! If you don't have a board available, NuttX has its own simulator that you can run on terminal.
Documentation
You can find the current NuttX documentation on the Documentation Page.
Alternatively, you can build the documentation yourself by following the Documentation Build Instructions.
The old NuttX documentation is still available in the Apache wiki.
Supported Boards
NuttX supports a wide variety of platforms. See the full list on the Supported Platforms page.
Contributing
If you wish to contribute to the NuttX project, read the Contributing guidelines for information on Git usage, coding standard, workflow and the NuttX principles.
License
The code in this repository is under either the Apache 2 license, or a license compatible with the Apache 2 license. See the License Page for more information.