Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Currently we force a synchronous call to __nfs_revalidate_inode() in
nfs_inode_set_delegation(). This not only ensures that we cannot call
nfs_inode_set_delegation from an asynchronous context, but it also slows
down any call to open().
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

There appear to be some rogue servers out there that issue multiple
delegations with different stateids for the same file. Ensure that when we
return delegations, we do so on a per-stateid basis rather than a per-file
basis.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Don't clobber the delegation info...
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

This ensures that nfs4_open_release() and nfs4_open_confirm_release()
can now handle an eventual delegation that was returned with out open.
As such, it fixes a delegation "leak" when the user breaks out of an open
call.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

The test for state->state == 0 does not tell you that the stateid is in the
process of being freed. It really tells you that the stateid is not yet
initialised...
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Currently we do not check for the FMODE_EXEC flag as we should. For that
particular case, we need to perform an ACCESS call to the server in order
to check that the file is executable.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Currently we just use a 32-bit counter.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

It is a void function...
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Also fix up the underestimate of fs_locations
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

The maximum size depends on the filename size and a number of other
elements which are currently not being counted.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

That just confuses certain NFSv4 servers.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

There is no justification for keeping a special spinlock for the exclusive
use of the NFS writeback code.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

They differ only slightly in the arguments they take. Why have they not
been merged?
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Convert them into dprintk() calls.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Do so by set the gc_proc field to RPC_GSS_PROC_DESTROY, and then sending a
NULL RPC call.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Add a refcount in order to ensure that the gss_auth doesn't disappear from
underneath us while we're freeing up GSS contexts.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

We should almost always be deferencing the rpc_auth struct by means of the
credential's cr_auth field instead of the rpc_clnt->cl_auth anyway. Fix up
that historical mistake, and remove the macro that propagated it.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

RPCSEC_GSS needs to be able to send NULL RPC calls to the server in order
to free up any remaining GSS contexts.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Convert to the use of atomic bitops...
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Add a helper rpc_cred_init()
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Also do the same for gss_api operation tables.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Does a NULL RPC call and returns a pointer to the resulting rpc_task. The
call may be either synchronous or asynchronous.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

See the FIXME: auth_flavors[] really needs a lock and module refcounting.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

Fix a memory leak in gss_create() whereby the rpc credcache was not being
freed if the rpc_mkpipe() call failed.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

We want to set the unix_cred_cache.nextgc on the first call to
unx_create(), which should be when unix_auth.au_count === 1
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

The leak only affects the RPCSEC_GSS caches, since they are the only ones
that are dynamically allocated...
Rename the existing rpcauth_free_credcache() to rpcauth_clear_credcache()
in order to better describe its role, then add a new function
rpcauth_destroy_credcache() that actually frees the cache in addition to
clearing it out.

Also move the call to destroy the credcache in gss_destroy() to come before
the rpc upcall pipe is unlinked.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>

This allows us to correctly deduce when we need to remove the pipe.
Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>