Wrong order of arguments in header.

It is called from KernelInterface with Mount(&fs, server, serverName, path..
That is also what FileSystem.cpp says.

kernel: atomic_*() functions rework

* No need for the atomically changed variables to be declared as
volatile.
* Drop support for atomically getting and setting unaligned data.
* Introduce atomic_get_and_set[64]() which works the same as
atomic_set[64]() used to. atomic_set[64]() does not return the
previous value anymore.

nfs4: Ignore superfluous slashes and get proper NFS4 share name

nfs4: support hard links properly

The main purpose of this patch is to prevent VFS from removing a vnode to early
what might have happened if the NFS client knew it had more than one name but
then one of them was deleted. Moreover, all discovered and still valid names
are stored what may be useful in proper file handle recovery when they are
volatile.

This patch fixes both #9558 and #9561.

nfs4: Allow customization of DirectoryCache expiration time

nfs4: Fix few Inode::fOpenState related race conditions

nfs4: Make request time limit adjustable

nfs4: Remove CacheRevalidator

There is no point in periodically revalidating all existing directory caches.
Directory snapshot can be revalidated when readdir is invoked.

nfs4: Use DoublyLinkedList instead of custom FileSystem list implementation

nfs4: Introduce VnodeToInode mapping

VnodeToInode is another abstraction layer between VFS vnodes and NFS nodes.
It simplifies dealing with race conditions as well as faking some guarantees
VFS expects but NFS does not provide.

nfs4: Fix race condition between inode creation and removal

If the underlying file system reuses inode numbers it is possible that
an entry of inode with reused id in InodeIdMap will be removed.
This patch should also improve behavior when one of many hard links
is removed.

nfs4: Add numerous assertion checks

nfs4: Make the client more configurable

nfs4: Do not repeat OPENATTR requests if not supported

nfs4: Make sure that request are properly sequenced

nfs4: Fix server reboot recovery

nfs4: Recall all delegations when callback path is down

nfs4: Reclaim delegations after server reboot

nfs4: Return delegations when asked to

nfs4: Use global open owner, check whether delegation was granted

nfs4: Add directory and name basic implementation

nfs4: Cache file attributes and filesystem info

nfs4: Rename Filehandle to FileHandle and Filesystem to FileSystem

kernel: atomic_*() functions rework

* No need for the atomically changed variables to be declared as
volatile.
* Drop support for atomically getting and setting unaligned data.
* Introduce atomic_get_and_set[64]() which works the same as
atomic_set[64]() used to. atomic_set[64]() does not return the
previous value anymore.

nfs4: Ignore superfluous slashes and get proper NFS4 share name

nfs4: support hard links properly

The main purpose of this patch is to prevent VFS from removing a vnode to early
what might have happened if the NFS client knew it had more than one name but
then one of them was deleted. Moreover, all discovered and still valid names
are stored what may be useful in proper file handle recovery when they are
volatile.

This patch fixes both #9558 and #9561.

nfs4: Allow customization of DirectoryCache expiration time

nfs4: Fix few Inode::fOpenState related race conditions

nfs4: Make request time limit adjustable

nfs4: Remove CacheRevalidator

There is no point in periodically revalidating all existing directory caches.
Directory snapshot can be revalidated when readdir is invoked.

nfs4: Use DoublyLinkedList instead of custom FileSystem list implementation

nfs4: Introduce VnodeToInode mapping

VnodeToInode is another abstraction layer between VFS vnodes and NFS nodes.
It simplifies dealing with race conditions as well as faking some guarantees
VFS expects but NFS does not provide.

nfs4: Fix race condition between inode creation and removal

If the underlying file system reuses inode numbers it is possible that
an entry of inode with reused id in InodeIdMap will be removed.
This patch should also improve behavior when one of many hard links
is removed.

nfs4: Add numerous assertion checks

nfs4: Make the client more configurable

nfs4: Do not repeat OPENATTR requests if not supported

nfs4: Make sure that request are properly sequenced

nfs4: Fix server reboot recovery

nfs4: Recall all delegations when callback path is down

nfs4: Reclaim delegations after server reboot

nfs4: Return delegations when asked to

nfs4: Use global open owner, check whether delegation was granted

nfs4: Add directory and name basic implementation

nfs4: Cache file attributes and filesystem info

nfs4: Rename Filehandle to FileHandle and Filesystem to FileSystem