syscalls/pipe: turn into a POSIX-style api with separate rw ends

Without separate read/write ends you can't tell when there are no more writers left if you have multiple readers. Consider this piece of code:
	int fd = pipe();
	fork(); // execution continues in 2 processes
	while (read(fd, &some_buf, sizeof somebuf) >= 0) {
		...
	}

Once both processes call `read()`, it's obvious that no writes are possible - all the processes that hold a reference to the pipe are currently stuck on a `read()` call, so the kernel could just make it return an error in both. But, what then? It's still possible to write to the pipe, and you can't know if the other process will do that. Thus, if you don't want to miss any output, you have to keep reading the pipe. Forever. Both processes end up stuck.

Having separate read/write ends prevents that.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/shared/syscalls.h b/src/shared/syscalls.h
index c6d3c33..f19f05a 100644
--- a/src/shared/syscalls.h
+++ b/src/shared/syscalls.h
@@ -82,6 +82,6 @@ int _syscall_fs_respond(void __user *buf, int ret, int flags);
  * @return address of the first affected page (usually == addr)
  */
 void __user *_syscall_memflag(void __user *addr, size_t len, int flags);
-handle_t _syscall_pipe(int flags);
+int _syscall_pipe(handle_t __user user_ends[2], int flags);
 
 void _syscall_debug_klog(const void __user *buf, size_t len);