Age | Commit message (Collapse) | Author |
|
thanks to this, the fs provider can continue executing until the next
fs_wait() call. that should speed things up a bit
|
|
|
|
|
|
awaited_req is a garbage name but i couldn't come up with a better one.
i also have no idea how to handle all the failure states
|
|
|
|
|
|
|
|
|
|
this was already possible, but now it's slightly safer
|
|
|
|
|
|
|
|
this will be needed for storing vfs_op's properly
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
this avoid accidental dereferences, and now it's easy to tell apart
which pointers are safe to directly read and which aren't.
cons:
- const is completely discarded
|
|
`()` means that any amt of arguments will be accepted, which isn't what
i want
|
|
|
|
|
|
|
|
|
|
|
|
it occureed if the path_simplify returned a negative value - instead of
being interpreter as an error it just carried on, ending up in an
infinite loop.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The length is a int, because the syscall will have a signed output. A
negative return value will mean an error (such as when it gets called
by a childless process).
|