a9148abd9d
and server. This replaces the RPC implementation of the NFS client and server with the newer RPC implementation originally developed (actually ported from the userland sunrpc code) to support the NFS Lock Manager. I have tested this code extensively and I believe it is stable and that performance is at least equal to the legacy RPC implementation. The NFS code currently contains support for both the new RPC implementation and the older legacy implementation inherited from the original NFS codebase. The default is to use the new implementation - add the NFS_LEGACYRPC option to fall back to the old code. When I merge this support back to RELENG_7, I will probably change this so that users have to 'opt in' to get the new code. To use RPCSEC_GSS on either client or server, you must build a kernel which includes the KGSSAPI option and the crypto device. On the userland side, you must build at least a new libc, mountd, mount_nfs and gssd. You must install new versions of /etc/rc.d/gssd and /etc/rc.d/nfsd and add 'gssd_enable=YES' to /etc/rc.conf. As long as gssd is running, you should be able to mount an NFS filesystem from a server that requires RPCSEC_GSS authentication. The mount itself can happen without any kerberos credentials but all access to the filesystem will be denied unless the accessing user has a valid ticket file in the standard place (/tmp/krb5cc_<uid>). There is currently no support for situations where the ticket file is in a different place, such as when the user logged in via SSH and has delegated credentials from that login. This restriction is also present in Solaris and Linux. In theory, we could improve this in future, possibly using Brooks Davis' implementation of variant symlinks. Supporting RPCSEC_GSS on a server is nearly as simple. You must create service creds for the server in the form 'nfs/<fqdn>@<REALM>' and install them in /etc/krb5.keytab. The standard heimdal utility ktutil makes this fairly easy. After the service creds have been created, you can add a '-sec=krb5' option to /etc/exports and restart both mountd and nfsd. The only other difference an administrator should notice is that nfsd doesn't fork to create service threads any more. In normal operation, there will be two nfsd processes, one in userland waiting for TCP connections and one in the kernel handling requests. The latter process will create as many kthreads as required - these should be visible via 'top -H'. The code has some support for varying the number of service threads according to load but initially at least, nfsd uses a fixed number of threads according to the value supplied to its '-n' option. Sponsored by: Isilon Systems MFC after: 1 month
86 lines
3.1 KiB
C
86 lines
3.1 KiB
C
/*-
|
|
* Copyright (c) 2008 Isilon Inc http://www.isilon.com/
|
|
* Authors: Doug Rabson <dfr@rabson.org>
|
|
* Developed with Red Inc: Alfred Perlstein <alfred@freebsd.org>
|
|
*
|
|
* 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 _RPC_REPLAY_H
|
|
#define _RPC_REPLAY_H
|
|
|
|
enum replay_state {
|
|
RS_NEW, /* new request - caller should execute */
|
|
RS_DONE, /* request was executed and reply sent */
|
|
RS_INPROGRESS, /* request is being executed now */
|
|
RS_ERROR /* allocation or other failure */
|
|
};
|
|
|
|
struct replay_cache;
|
|
|
|
/*
|
|
* Create a new replay cache.
|
|
*/
|
|
struct replay_cache *replay_newcache(size_t);
|
|
|
|
/*
|
|
* Set the replay cache size.
|
|
*/
|
|
void replay_setsize(struct replay_cache *, size_t);
|
|
|
|
/*
|
|
* Free a replay cache. Caller must ensure that no cache entries are
|
|
* in-progress.
|
|
*/
|
|
void replay_freecache(struct replay_cache *rc);
|
|
|
|
/*
|
|
* Check a replay cache for a message from a given address.
|
|
*
|
|
* If this is a new request, RS_NEW is returned. Caller should call
|
|
* replay_setreply with the results of the request.
|
|
*
|
|
* If this is a request which is currently executing
|
|
* (i.e. replay_setreply hasn't been called for it yet), RS_INPROGRESS
|
|
* is returned. The caller should silently drop the request.
|
|
*
|
|
* If a reply to this message already exists, *repmsg and *mp are set
|
|
* to point at the reply and, RS_DONE is returned. The caller should
|
|
* re-send this reply.
|
|
*
|
|
* If the attempt to update the replay cache or copy a replay failed
|
|
* for some reason (typically memory shortage), RS_ERROR is returned.
|
|
*/
|
|
enum replay_state replay_find(struct replay_cache *rc,
|
|
struct rpc_msg *msg, struct sockaddr *addr,
|
|
struct rpc_msg *repmsg, struct mbuf **mp);
|
|
|
|
/*
|
|
* Call this after executing a request to record the reply.
|
|
*/
|
|
void replay_setreply(struct replay_cache *rc,
|
|
struct rpc_msg *repmsg, struct sockaddr *addr, struct mbuf *m);
|
|
|
|
#endif /* !_RPC_REPLAY_H */
|