Home
last modified time | relevance | path

Searched full:nfsv4 (Results 1 – 25 of 68) sorted by relevance

123

/linux/Documentation/filesystems/nfs/
H A Dclient-identifier.rst4 NFSv4 client identifier
7 This document explains how the NFSv4 protocol identifies client
14 There are risks if a client's NFSv4 identifier and its principal
21 The NFSv4 protocol uses "lease-based file locking". Leases help
22 NFSv4 servers provide file lock guarantees and manage their
25 Simply put, an NFSv4 server creates a lease for each NFSv4 client.
34 the NFSv4 protocol allows the server to remove the client's open
40 In addition, each NFSv4 server manages a persistent list of client
47 NFSv4 client identifiers
50 Each NFSv4 client presents an identifier to NFSv4 servers so that
[all …]
H A Drpc-server-gss.rst7 server and the NFS client's NFSv4.0 callback server. (But note that
8 NFSv4.1 and higher don't require the client to act as a server for the
H A Dnfs41-server.rst2 NFSv4.1 Server Implementation
21 The NFSv4 minorversion 1 (NFSv4.1) implementation in nfsd is based
24 From the many new features in NFSv4.1 the current implementation
25 focuses on the mandatory-to-implement NFSv4.1 Sessions, providing
29 The table below, taken from the NFSv4.1 document, lists
31 (OPT), and NFSv4.0 operations that are required not to implement (MNI)
43 - **I** Implemented NFSv4.1 operations.
/linux/fs/nfs/
H A DKconfig86 To mount NFS servers using NFSv4, you also need to install user
101 bool "NFS client support for NFSv4.0"
105 This option enables support for minor version 0 of the NFSv4 protocol
111 bool "NFS client support for NFSv4.2"
114 This option enables support for minor version 2 of the NFSv4 protocol
135 string "NFSv4.1 Implementation ID Domain"
147 bool "NFSv4.1 client support for migration"
151 This option makes the NFS client advertise to NFSv4.1 servers that
152 it can support NFSv4 migration.
154 The NFSv4.1 pieces of the Linux NFSv4 migration implementation are
[all …]
H A Dcallback.c7 * NFSv4 callback handling
72 * This is the NFSv4 callback kernel thread.
278 /* No RPC_AUTH_GSS on NFSv4.1 back channel yet */ in check_gss_callback_principal()
311 * pg_authenticate method for nfsv4 callback threads.
329 /* No RPC_AUTH_GSS support yet in NFSv4.1 */ in nfs_callback_authenticate()
350 .pg_name = "NFSv4 callback", /* service name */
H A Dnfs4client.c27 * Get a unique NFSv4.0 callback identifier which will be used
333 * nfs41_init_client - nfs_client initialization tasks for NFSv4.1+
495 /* NFSv4.1 always uses the uniform string, however someone in nfs4_match_client()
645 * NFSv4.0 callback thread helper
686 * NFSv4.1 callback thread helper
919 /* data servers support only a subset of NFSv4.1 */ in nfs4_server_common_setup()
1147 * Either its session is drained (NFSv4.1+), or its transport is
1148 * plugged and drained (NFSv4.0).
H A Dnfs40client.c58 * nfs40_init_client - nfs_client initialization tasks for NFSv4.0
73 "NFSv4.0 transport Slot table"); in nfs40_init_client()
H A Dnfs4super.c58 * Clean out any remaining NFSv4 state that might be left over due
313 MODULE_DESCRIPTION("NFSv4 client support");
/linux/Documentation/admin-guide/nfs/
H A Dnfs-client.rst10 being documented in RFC1813 (June 1995), and NFSv4 in RFC3530 (April
14 and work is in progress on adding support for minor version 1 of the NFSv4
25 NFSv4 requires clients to identify themselves to servers with a unique
27 is associated with this identity. To support robust NFSv4 state recovery
51 outstanding NFSv4 state has expired, to prevent loss of NFSv4 state.
66 NFSv4 allows for one server to refer the NFS client to data that has been
69 `Implementation Guide for Referrals in NFSv4`_.
72 .. _Implementation Guide for Referrals in NFSv4: https://tools.ietf.org/html/draft-ietf-nfsv4-refer…
/linux/fs/nfsd/
H A Dnetns.h53 NFSD_STATS_FIRST_NFS4_OP, /* count of individual nfsv4 operations */
61 * Per-netns NFSv4 callback (backchannel) per-operation counters, indexed
67 * Represents a nfsd "container". With respect to nfsv4 state tracking, the
209 /* Per-netns NFSv4 callback (backchannel) per-operation counters */
244 /* last time an admin-revoke happened for NFSv4.0 */
H A Dnfs4idmap.c53 "Turn off server's NFSv4 idmapping when using 'sec=sys'");
180 printk("nfsd: nfsv4 idmapping failing: has idmapd %s?\n", in warn_no_idmapd()
654 * Returns nfs_ok on success or an NFSv4 status code on failure.
666 * NFSv4 servers are not permitted to drop requests. Also in nfsd_map_name_to_uid()
667 * RQ_DROPME will force NFSv4.1 session slot processing to in nfsd_map_name_to_uid()
691 * Returns nfs_ok on success or an NFSv4 status code on failure.
703 * NFSv4 servers are not permitted to drop requests. Also in nfsd_map_name_to_gid()
704 * RQ_DROPME will force NFSv4.1 session slot processing to in nfsd_map_name_to_gid()
H A Dattr4.h3 * NFSv4 file attributes supported by this implementation
140 * This mask includes NFSv4.2-only attributes (e.g., POSIX ACLs).
H A Dflexfilelayout.c6 * where the NFSv4.1 mds is also the ds. And the storage is
7 * the same. I.e., writing to the mds via a NFSv4.1 WRITE
H A Dnfs4callback.c72 * Encode/decode NFSv4 CB basic data types
74 * Basic NFSv4 callback data types are defined in section 15 of RFC
231 * Note: remaining NFSv4 error codes have values > 10000, so should
619 * NFSv4.0 and NFSv4.1 XDR encode functions
621 * NFSv4.0 callback argument types are defined in section 15 of RFC
697 * NFSv4.0 and NFSv4.1 XDR decode functions
699 * NFSv4.0 callback result types are defined in section 15 of RFC
H A Dnfsfh.h105 * pre-op nfsv4 change attr: note must check IS_I_VERSION(inode)
112 u64 fh_post_change; /* nfsv4 change; see above */
/linux/include/linux/
H A Dnfs4.h5 * NFSv4 protocol definitions.
233 * New to NFSv4.1. If session is persistent,
276 * "XDR Description of NFSv4.0"
339 * "XDR Description of NFSv4.1"
367 * "XDR Description of NFSv4.2"
393 * Symbol name and value are from draft-ietf-nfsv4-uncacheable-files
418 /* Mandatory in NFSv4.1 */
782 /* Callback operations new to NFSv4.1 */
794 /* Callback operations new to NFSv4.2 */
/linux/Documentation/sunrpc/xdr/
H A Dnfs4_1.x69 * meaning in NFSv4.x.
100 /* NFS4ERR_RESOURCE is not a valid error in NFSv4.1 */
134 /* NFSv4.1 errors start here. */
229 * The following content was extracted from draft-ietf-nfsv4-delstid
353 * The following content was extracted from draft-ietf-nfsv4-posix-acls
/linux/fs/nfs_common/
H A Dcommon.c120 * This one is used by NFSv4.
142 * Note: remaining NFSv4 error codes have values > 10000, so should in nfs4_stat_to_errno()
195 * Note: remaining NFSv4 error codes have values > 10000, so should in nfs_localio_errno_to_nfs4_stat()
/linux/include/linux/sunrpc/
H A Dsvc_xprt.h44 * an xprt; intended for use by NFSv4.1, which needs to know when a
80 struct rpc_xprt *xpt_bc_xprt; /* NFSv4.1 backchannel */
81 struct rpc_xprt_switch *xpt_bc_xps; /* NFSv4.1 backchannel */
/linux/fs/nfs/filelayout/
H A Dfilelayoutdev.c300 MODULE_PARM_DESC(dataserver_retrans, "The number of times the NFSv4.1 client "
305 "NFSv4.1 client waits for a response from a "
H A Dfilelayout.h2 * NFSv4 file layout driver data structures.
/linux/include/uapi/linux/
H A Dnfs4_mount.h10 * structure passed from user-space to kernel-space during an nfsv4 mount
H A Dnfs_mount.h63 #define NFS_MOUNT_STRICTLOCK 0x1000 /* reserved for NFSv4 */
/linux/net/sunrpc/
H A Daddr.c9 * recent RFCs describing NFSv4. The universal address format is part
11 * and 4, and by NFSv4. Such an address is a string containing a
/linux/Documentation/netlink/specs/
H A Dnfsd.yaml327 Export path whose NFSv4 state should be revoked.
593 Revoke NFSv4 state acquired through exports of a given path.

123