SUNRPC: Define rpcsec_gss_info structure
authorChuck Lever <chuck.lever@oracle.com>
Sat, 16 Mar 2013 19:54:34 +0000 (15:54 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Fri, 29 Mar 2013 19:42:56 +0000 (15:42 -0400)
commitfb15b26f8ba3ff629a052faf3f4a4744585ca2dc
tree2218a2e577bf075170497549847d49840f296aae
parent72f4dc117b57e05120aaac6e218b8abc09a5c350
SUNRPC: Define rpcsec_gss_info structure

The NFSv4 SECINFO procedure returns a list of security flavors.  Any
GSS flavor also has a GSS tuple containing an OID, a quality-of-
protection value, and a service value, which specifies a particular
GSS pseudoflavor.

For simplicity and efficiency, I'd like to return each GSS tuple
from the NFSv4 SECINFO XDR decoder and pass it straight into the RPC
client.

Define a data structure that is visible to both the NFS client and
the RPC client.  Take structure and field names from the relevant
standards to avoid confusion.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/nfs4namespace.c
fs/nfs/nfs4xdr.c
include/linux/nfs_xdr.h
include/linux/sunrpc/gss_api.h
net/sunrpc/auth_gss/gss_krb5_mech.c
This page took 0.028359 seconds and 5 git commands to generate.