summaryrefslogtreecommitdiff
path: root/Kernel/Syscalls/umask.cpp
diff options
context:
space:
mode:
authorLiav A <liavalb@gmail.com>2021-08-07 22:30:06 +0300
committerAndreas Kling <kling@serenityos.org>2021-08-12 20:57:32 +0200
commit01b79910b3b881c26a972487fddb4251682438f5 (patch)
tree28e3b7fe5ba9d1260e8da5df431042f50780c186 /Kernel/Syscalls/umask.cpp
parente405f436b69afd9cf553321c59c06f92eefaa239 (diff)
downloadserenity-01b79910b3b881c26a972487fddb4251682438f5.zip
Kernel/Process: Move protected values to the end of the object
The compiler can re-order the structure (class) members if that's necessary, so if we make Process to inherit from ProcFSExposedComponent, even if the declaration is to inherit first from ProcessBase, then from ProcFSExposedComponent and last from Weakable<Process>, the members of class ProcFSExposedComponent (including the Ref-counted parts) are the first members of the Process class. This problem made it impossible to safely use the current toggling method with the write-protection bit on the ProcessBase members, so instead of inheriting from it, we make its members the last ones in the Process class so we can safely locate and modify the corresponding page write protection bit of these values. We make sure that the Process class doesn't expand beyond 8192 bytes and the protected values are always aligned on a page boundary.
Diffstat (limited to 'Kernel/Syscalls/umask.cpp')
-rw-r--r--Kernel/Syscalls/umask.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/Kernel/Syscalls/umask.cpp b/Kernel/Syscalls/umask.cpp
index 16819f0215..e019fb0344 100644
--- a/Kernel/Syscalls/umask.cpp
+++ b/Kernel/Syscalls/umask.cpp
@@ -12,9 +12,9 @@ KResultOr<FlatPtr> Process::sys$umask(mode_t mask)
{
VERIFY_PROCESS_BIG_LOCK_ACQUIRED(this)
REQUIRE_PROMISE(stdio);
- auto old_mask = m_umask;
+ auto old_mask = m_protected_values.umask;
ProtectedDataMutationScope scope { *this };
- m_umask = mask & 0777;
+ m_protected_values.umask = mask & 0777;
return old_mask;
}