Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
thus they can opt out of doing that
so the calls which might return immediately but can return later don't
have to both regs_savereturn and return to the caller.
and because of that, the return values of a lot of VFS things have just
got way saner
|
|
|
|
|
|
|
|
...instead of letting the hwole process stay around.
This could end up a bit more complex, I have no idea how to test killing
processes during vfs requests.
The upside of this is that I can remove all the deathbed/deadparent
weirdness now.
|
|
what a mess
|
|
|
|
|
|
|
|
|
|
|
|
handling the backend queue makes more sense here than in the syscall
implementation. it's also just overall cleaner
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
thanks to this i can tell which ones are placeholders, and which ones
should stay
|
|
|
|
|
|
|
|
the kfree() call was freeing a buffer which was inside a process struct
|
|
|
|
|
|
|
|
the values are the same, it only caused a warning in sparse
|
|
|
|
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
|
|
|
|
|