From d8376efdc12495bb78b440ba27ab89bb53beb489 Mon Sep 17 00:00:00 2001 From: Xiang Xiao Date: Mon, 29 Jun 2020 13:54:01 +0800 Subject: [PATCH] nxsched_release_tcb: Should release stack in kernel build too otherwise the memory can't be reused util the process exit Signed-off-by: Xiang Xiao --- sched/sched/sched_releasetcb.c | 17 +---------------- 1 file changed, 1 insertion(+), 16 deletions(-) diff --git a/sched/sched/sched_releasetcb.c b/sched/sched/sched_releasetcb.c index 00e6355642..45d3d0ae18 100644 --- a/sched/sched/sched_releasetcb.c +++ b/sched/sched/sched_releasetcb.c @@ -134,22 +134,7 @@ int nxsched_release_tcb(FAR struct tcb_s *tcb, uint8_t ttype) if (tcb->stack_alloc_ptr && (tcb->flags & TCB_FLAG_CUSTOM_STACK) == 0) { -#ifdef CONFIG_BUILD_KERNEL - /* 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); - } + up_release_stack(tcb, ttype); } #ifdef CONFIG_PIC