Message types for VFS unlink & rmdir

These two request are handled by the same function in some FSes, which
prevents us from using two different kinds of messages.

Change-Id: Iede3a0251d8d84ca7f121

Message types for VFS unlink & rmdir

These two request are handled by the same function in some FSes, which
prevents us from using two different kinds of messages.

Change-Id: Iede3a0251d8d84ca7f121c56f30f42b045b0c737

show more ...

Message types for VFS stat

Change-Id: I1d40ae7c3c32a4f7b80c82bc2fa8b157b20a6837

Message types for VFS inhibread

Change-Id: I4ce20a4566033593e4784fd278d7ff7fda16dd9d

Message types for VFS putnode

Change-Id: I0802ccaaaa6ee1b4eb96d62b08f9795c790ce39b

Message types for VFS link

Change-Id: Ibe03e7c9fded7f3764ecbe3e35b92df3662e54a4

Message types for VFS rdlink

Change-Id: Ic077e99fb140a3a1de849f7f761fdfd90961f5d8

Message types for VFS getdents

Change-Id: I7474d7547f1fd52f4da54754ccfe984ba1a2baa8

Message types for VFS new_driver

Change-Id: If1b6ee2c5beb43e72a69c27dbc32b72525831962

Message types for VFS slink

Change-Id: I13975474b924817553101c28591b4c04e8679173

Message types for VFS utime

Change-Id: If7e5faa13a824528fd8ca02bd6982e04d48032e9

Message types for VFS ftrunc

Change-Id: I593a4d91b1d974f632f6cb4eb23aabee5b65df7b

Message types for VFS rename

Change-Id: I48a4098c16519e9c104b287d7bdf95ed6a2a7323

Message types for VFS flush

Change-Id: Ida7cbff4402bf876603a2153e2784699d93c03ea

Message types for VFS mountpoint

Change-Id: I61c5729628b9b9262cc11415591b1b0f25ad04a8

Message types for VFS newnode

Change-Id: I5c0790fc1104182ab08bcae699c60a364833c360

Message types for VFS create

Change-Id: Ibeba338337eb16814b5b25f7135da958e8316a99

Message types for VFS lookup

Change-Id: Ic4d2a616ebc986c4b405b6b9ee0bd7c3b59e81d2

Message types for VFS readsuper

Change-Id: I7aea85d9842459ea454420bb1687d9b8eb597914

Remove unused generic message m6

Change-Id: Ie99dca9b75325b3c4890718f8ac7aa49a8973798

Introduce message types mess_u{8,16,32,64}

Those messages offer a simple array of the given type. This should allow
for fast and simple prototyping.

When a protocol is fixed, then proper message ty

Introduce message types mess_u{8,16,32,64}

Those messages offer a simple array of the given type. This should allow
for fast and simple prototyping.

When a protocol is fixed, then proper message types should be defined.

Change-Id: I4e98eeb0493924f3015862a51d14d894315e2bc2

show more ...

added sethostname syscall with proper error checks

Change-Id: I4b4e0a7c4035e19d5843b86ee1f714096adcecd2

Stub for setpgid

This implements a near noop setpgid, unless the use is one equivalent
to setsid, in which case it will behave as such.

Also activates setpgrp, which is implemented in terms of setp

Stub for setpgid

This implements a near noop setpgid, unless the use is one equivalent
to setsid, in which case it will behave as such.

Also activates setpgrp, which is implemented in terms of setpgid.

Change-Id: I84411cb1957351aa1d3985623cd9e69bdf6f8d4c

show more ...

Workaround missing lchmod/lchown

Change-Id: I231a0010722619d389b763af35ff55f84ca9cb76

_MINIX_SYSTEM - fixes for in-minix crossbuild

. define _MINIX_SYSTEM for all system code from minix.service.mk
. hide some system-level declarations and definitions
behind _MINIX_SYSTEM to clea

_MINIX_SYSTEM - fixes for in-minix crossbuild

. define _MINIX_SYSTEM for all system code from minix.service.mk
. hide some system-level declarations and definitions
behind _MINIX_SYSTEM to cleanly fix host tool build problems on
Minix (such as: NONE being defined and paddr_t being used but not
declared)
. the similar definition _SYSTEM is unsuitable as it changes the
values of errno definitions

Change-Id: I407de79e2575115243a074b16e79546a279cfa3e

show more ...

make vfs & filesystems use failable copying

Change the kernel to add features to vircopy and safecopies so that
transparent copy fixing won't happen to avoid deadlocks, and such copies
fail with EFA

make vfs & filesystems use failable copying

Change the kernel to add features to vircopy and safecopies so that
transparent copy fixing won't happen to avoid deadlocks, and such copies
fail with EFAULT.

Transparently making copying work from filesystems (as normally done by
the kernel & VM when copying fails because of missing/readonly memory)
is problematic as it can happen that, for file-mapped ranges, that that
same filesystem that is blocked on the copy request is needed to satisfy
the memory range, leading to deadlock. Dito for VFS itself, if done with
a blocking call.

This change makes the copying done from a filesystem fail in such cases
with EFAULT by VFS adding the CPF_TRY flag to the grants. If a FS call
fails with EFAULT, VFS will then request the range to be made available
to VM after the FS is unblocked, allowing it to be used to satisfy the
range if need be in another VFS thread.

Similarly, for datacopies that VFS itself does, it uses the failable
vircopy variant and callers use a wrapper that talk to VM if necessary
to get the copy to work.

. kernel: add CPF_TRY flag to safecopies
. kernel: only request writable ranges to VM for the
target buffer when copying fails
. do copying in VFS TRY-first
. some fixes in VM to build SANITYCHECK mode
. add regression test for the cases where
- a FS system call needs memory mapped in a process that the
FS itself must map.
- such a range covers more than one file-mapped region.
. add 'try' mode to vircopy, physcopy
. add flags field to copy kernel call messages
. if CP_FLAG_TRY is set, do not transparently try
to fix memory ranges
. for use by VFS when accessing user buffers to avoid
deadlock
. remove some obsolete backwards compatability assignments
. VFS: let thread scheduling work for VM requests too
Allows VFS to make calls to VM while suspending and resuming
the currently running thread. Does currently not work for the
main thread.
. VM: add fix memory range call for use by VFS

Change-Id: I295794269cea51a3163519a9cfe5901301d90b32

show more ...