Why"vTaskEnterCritical" and "vTaskExitCritical" designed not symmetry on interrupt status sematics?

Kernel
1

Hi folks:
this is the current “vTaskExitCritical” and “vTaskEnterCritical”.

    void vTaskEnterCritical( void )
    {
         portDISABLE_INTERRUPTS();
         .............
    }
    and
   void vTaskExitCritical( void )
   {
         if( xSchedulerRunning != pdFALSE )
         {
                  if (...)
                  {
                         portENABLE_INTERRUPTS();
                   }
          }
   }

you see, portDISABLE_INTERRUPTS is unconditinal exectuted,but the enable flow executed with the condition xSchedulerRunning = true.
would this cause a un-symmetry during bootup stage when xSchedulerRunning is false?
thank you!

2

Interrupts are deliberately left disabled between the first call to a FreeRTOS API call and the scheduler being started. This is to avoid a very common issue users had in the early days of FreeRTOS where interrupts tried to use the scheduler before it had been started.

3

thank you very much!