From 546cdde776e88635b9faf9996d753a5eccaf9bfa Mon Sep 17 00:00:00 2001
From: Ben Wiederhake <BenWiederhake.GitHub@gmx.de>
Date: Fri, 12 Feb 2021 18:49:16 +0100
Subject: [PATCH] Kernel: clock_nanosleep's 'flags' is not a bitset

This had the interesting effect that most, but not all, non-zero values
were interpreted as an absolute value.
---
 Kernel/Syscalls/clock.cpp | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/Kernel/Syscalls/clock.cpp b/Kernel/Syscalls/clock.cpp
index c28552953d..557d9376ce 100644
--- a/Kernel/Syscalls/clock.cpp
+++ b/Kernel/Syscalls/clock.cpp
@@ -76,7 +76,17 @@ int Process::sys$clock_nanosleep(Userspace<const Syscall::SC_clock_nanosleep_par
     if (!copy_from_user(&requested_sleep, params.requested_sleep))
         return -EFAULT;
 
-    bool is_absolute = params.flags & TIMER_ABSTIME;
+    bool is_absolute;
+    switch (params.flags) {
+    case 0:
+        is_absolute = false;
+        break;
+    case TIMER_ABSTIME:
+        is_absolute = true;
+        break;
+    default:
+        return -EINVAL;
+    }
 
     if (!TimeManagement::is_valid_clock_id(params.clock_id))
         return -EINVAL;