freebsd-dev/sys/fs/nfs/nfsv4_errstr.h
Rick Macklem 9ec7b004d0 Add the experimental nfs subtree to the kernel, that includes
support for NFSv4 as well as NFSv2 and 3.
	It lives in 3 subdirs under sys/fs:
	nfs - functions that are common to the client and server
	nfsclient - a mutation of sys/nfsclient that call generic functions
	to do RPCs and handle state. As such, it retains the
	buffer cache handling characteristics and vnode semantics that
	are found in sys/nfsclient, for the most part.
	nfsserver - the server. It includes a DRC designed specifically for
	NFSv4, that is used instead of the generic DRC in sys/rpc.
	The build glue will be checked in later, so at this point, it
	consists of 3 new subdirs that should not affect kernel building.

Approved by:	kib (mentor)
2009-05-04 15:23:58 +00:00

102 lines
3.1 KiB
C

/*-
* Copyright (c) 2009 Rick Macklem, University of Guelph
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* $FreeBSD$
*/
#ifndef _NFS_NFSV4ERRSTR_H_
#define _NFS_NFSV4ERRSTR_H_
/*
* Defines static storage in the C file, but I can't be bothered creating
* a library of one function for this, since it is only currently used by
* mount_newnfs.c.
*/
static const char *nfsv4_errstr[48] = {
"Illegal filehandle",
"Undefined NFSv4 err",
"READDIR cookie is stale",
"operation not supported",
"response limit exceeded",
"undefined server error",
"type invalid for CREATE",
"file busy - retry",
"nverify says attrs same",
"lock unavailable",
"lock lease expired",
"I/O failed due to lock",
"in grace period",
"filehandle expired",
"share reserve denied",
"wrong security flavor",
"clientid in use",
"resource exhaustion",
"filesystem relocated",
"current FH is not set",
"minor vers not supp",
"server has rebooted",
"server has rebooted",
"state is out of sync",
"incorrect stateid",
"request is out of seq",
"verify - attrs not same",
"lock range not supported",
"should be file/directory",
"no saved filehandle",
"some filesystem moved",
"recommended attr not sup",
"reclaim outside of grace",
"reclaim error at server",
"conflict on reclaim",
"XDR decode failed",
"file locks held at CLOSE",
"conflict in OPEN and I/O",
"owner translation bad",
"utf-8 char not supported",
"name not supported",
"lock range not supported",
"no atomic up/downgrade",
"undefined operation",
"file locking deadlock",
"open file blocks op",
"lockowner state revoked",
"callback path down"
};
/*
* Return the error string for the NFS4ERR_xxx. The pointers returned are
* static and must not be free'd.
*/
static const char *
nfsv4_geterrstr(int errval)
{
if (errval < NFSERR_BADHANDLE || errval > NFSERR_CBPATHDOWN)
return (NULL);
return (nfsv4_errstr[errval - NFSERR_BADHANDLE]);
}
#endif /* _NFS_NFSV4ERRSTR_H_ */