RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-05-31 10:48:11 +00:00
Code Issues Activity Actions

Okay let's just not have this broken locking at all right now.

Browse source 
I think I should just protect access to shared data structures
and eventually do read/write atomicity locks at the inode level.
This commit is contained in:
Andreas Kling 2018-10-29 22:43:39 +01:00
parent e6284a8774
commit b1ff62f605
7 changed files with 16 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Kernel/Syscall.cpp
View file

@ -2,7 +2,6 @@
#include "Task.h"
#include "Syscall.h"
#include "Console.h"
#include <AK/Lock.h>
extern "C" void syscall_entry();
extern "C" void syscall_ISR();
@ -100,7 +99,6 @@ DWORD handle(DWORD function, DWORD arg1, DWORD arg2, DWORD arg3)
return current->sys$gethostname((char*)arg1, (size_t)arg2);
case Syscall::PosixExit:
cli();
//locker.unlock();
current->sys$exit((int)arg1);
ASSERT_NOT_REACHED();
return 0;