diff options
author | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2013-01-13 00:35:47 +0000 |
---|---|---|
committer | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2013-01-13 00:35:47 +0000 |
commit | ffda55b34a9a8a4a84f4cbc1da3836b944baec46 (patch) | |
tree | f74938699bd760dbbba52578827f5e100d7b3700 /nuttx/ChangeLog | |
parent | b58281cab8add0af82167282126132b069170dd6 (diff) | |
download | px4-firmware-ffda55b34a9a8a4a84f4cbc1da3836b944baec46.tar.gz px4-firmware-ffda55b34a9a8a4a84f4cbc1da3836b944baec46.tar.bz2 px4-firmware-ffda55b34a9a8a4a84f4cbc1da3836b944baec46.zip |
Cosmetic cleanup from SIGCHLD changes
git-svn-id: http://svn.code.sf.net/p/nuttx/code/trunk@5514 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/ChangeLog')
-rw-r--r-- | nuttx/ChangeLog | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog index 921b7014b..7deb9fa94 100644 --- a/nuttx/ChangeLog +++ b/nuttx/ChangeLog @@ -3918,7 +3918,7 @@ the scenario: (1) sched_lock() is called increments the lockcount on the current TCB (i.e., the one at the head of the ready to run list), (2) sched_mergepending is called which may change the task - at the head of the readytorun list, then (2) sched_lock() is called + at the head of the readytorun list, then (2) sched_unlock() is called which decrements the lockcount on the wrong TCB. The failure case that I saw was that pre-emption got disabled in the IDLE thread, locking up the whole system. |