sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

nxsched_release_tcb: Should release stack in kernel build too

Browse Source 
otherwise the memory can't be reused util the process exit

Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
This commit is contained in:
Xiang Xiao 2020-06-29 13:54:01 +08:00 committed by patacongo
parent e87617f9fa
commit d8376efdc1
1 changed files with 1 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
sched/sched/sched_releasetcb.c
View File

@ -134,22 +134,7 @@ int nxsched_release_tcb(FAR struct tcb_s *tcb, uint8_t ttype)
if (tcb->stack_alloc_ptr && if (tcb->stack_alloc_ptr &&
(tcb->flags & TCB_FLAG_CUSTOM_STACK) == 0) (tcb->flags & TCB_FLAG_CUSTOM_STACK) == 0)
{ {
#ifdef CONFIG_BUILD_KERNEL up_release_stack(tcb, ttype);
/* If the exiting thread is not a kernel thread, then it has an
* address environment. Don't bother to release the stack memory
* in this case... There is no point since the memory lies in the
* user memory region that will be destroyed anyway (and the
* address environment has probably already been destroyed at
* this point.. so we would crash if we even tried it). But if
* this is a privileged group, when we still have to release the
* memory using the kernel allocator.
*/
if ((tcb->flags & TCB_FLAG_TTYPE_MASK) == TCB_FLAG_TTYPE_KERNEL)
#endif
{
up_release_stack(tcb, ttype);
}
} }
#ifdef CONFIG_PIC #ifdef CONFIG_PIC