From 31312817475d6b41a30c52b2ca520041e43a0084 Mon Sep 17 00:00:00 2001
From: Andreas Kling <kling@serenityos.org>
Date: Sun, 14 Feb 2021 10:48:04 +0100
Subject: [PATCH] Kernel: Panic on syscall from process with IOPL != 0

If this happens then the kernel is in an undefined state, so we should
rather panic than attempt to limp along.
---
 Kernel/Syscall.cpp | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/Kernel/Syscall.cpp b/Kernel/Syscall.cpp
index 62652008a5e..54c31b608d7 100644
--- a/Kernel/Syscall.cpp
+++ b/Kernel/Syscall.cpp
@@ -26,6 +26,7 @@
 
 #include <Kernel/API/Syscall.h>
 #include <Kernel/Arch/i386/CPU.h>
+#include <Kernel/Panic.h>
 #include <Kernel/Process.h>
 #include <Kernel/Random.h>
 #include <Kernel/ThreadTracer.h>
@@ -165,9 +166,7 @@ void syscall_handler(TrapFrame* trap)
     static constexpr u32 iopl_mask = 3u << 12;
 
     if ((regs.eflags & (iopl_mask)) != 0) {
-        dbgln("Syscall from process with IOPL != 0");
-        handle_crash(regs, "Non-zero IOPL on syscall entry", SIGSEGV);
-        ASSERT_NOT_REACHED();
+        PANIC("Syscall from process with IOPL != 0");
     }
 
     if (!MM.validate_user_stack(process, VirtualAddress(regs.userspace_esp))) {