nfs4: Improve tracing when DEBUG. Always show NFS errors

Change-Id: Idd6904258c479dc3d188bf245b1bae0d3849820b
Reviewed-on: https://review.haiku-os.org/c/haiku/+/3397
Reviewed-by: Adrien Destugues <pulkomandy@gmail.com>

nfs4: FileSystem::~FileSystem() make sure fServer is valid

nfs4: Ignore superfluous slashes and get proper NFS4 share name

nfs4: let nfs4 use kernel utils for random numbers

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: Make TRACE format strings 32/64 bit independent

nfs4: Try connecting to all getaddrinfo() results before giving up

nfs4: Fix few Inode::fOpenState related race conditions

nfs4: Avoid using empty string for RootInode name

nfs4: Use DoublyLinkedList instead of custom FileSystem list implementation

nfs4: FileSystem may be destroyed before setting RPCServer private data

nfs4: Expect file system root path to be NULL

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, dns_resolver: fix numerous style violations

nfs4: Fix file handle recovery

nfs4: Make the client more configurable

nfs4: Fix gcc4 warnings

nfs4: Let GenerateClientID take advantage of PeerAddress methods

nfs4: Do not repeat OPENATTR requests if not supported

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: Use IPPROTO_* instead of enum Transport

nfs4: Rename Filehandle to FileHandle and Filesystem to FileSystem

nfs4: FileSystem::~FileSystem() make sure fServer is valid

nfs4: Ignore superfluous slashes and get proper NFS4 share name

nfs4: let nfs4 use kernel utils for random numbers

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: Make TRACE format strings 32/64 bit independent

nfs4: Try connecting to all getaddrinfo() results before giving up

nfs4: Fix few Inode::fOpenState related race conditions

nfs4: Avoid using empty string for RootInode name

nfs4: Use DoublyLinkedList instead of custom FileSystem list implementation

nfs4: FileSystem may be destroyed before setting RPCServer private data

nfs4: Expect file system root path to be NULL

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, dns_resolver: fix numerous style violations

nfs4: Fix file handle recovery

nfs4: Make the client more configurable

nfs4: Fix gcc4 warnings

nfs4: Let GenerateClientID take advantage of PeerAddress methods

nfs4: Do not repeat OPENATTR requests if not supported

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: Use IPPROTO_* instead of enum Transport

nfs4: Rename Filehandle to FileHandle and Filesystem to FileSystem