summaryrefslogtreecommitdiff
path: root/Kernel
diff options
context:
space:
mode:
authorGunnar Beutner <gbeutner@serenityos.org>2021-06-07 11:00:58 +0200
committerAli Mohammad Pur <Ali.mpfard@gmail.com>2021-06-07 14:45:38 +0430
commit3bac14e19e6bf7df9019b71ff47aa34ab89e516f (patch)
tree53e88403f1102c550398f1ae26421d5b29409f9d /Kernel
parentcb295ab644875f87356df69385d2836dab8a1120 (diff)
downloadserenity-3bac14e19e6bf7df9019b71ff47aa34ab89e516f.zip
Kernel: Remove incorrect VERIFY() in Thread::relock_process
Turns are there are legitimate cases where the thread state isn't Thread::Running.
Diffstat (limited to 'Kernel')
-rw-r--r--Kernel/Thread.cpp2
1 files changed, 0 insertions, 2 deletions
diff --git a/Kernel/Thread.cpp b/Kernel/Thread.cpp
index e25377aacb..9025730002 100644
--- a/Kernel/Thread.cpp
+++ b/Kernel/Thread.cpp
@@ -326,8 +326,6 @@ LockMode Thread::unlock_process_if_locked(u32& lock_count_to_restore)
void Thread::relock_process(LockMode previous_locked, u32 lock_count_to_restore)
{
- VERIFY(state() == Thread::Running);
-
// Clearing the critical section may trigger the context switch
// flagged by calling Scheduler::donate_to or Scheduler::yield
// above. We have to do it this way because we intentionally