Lines Matching +full:per +full:- +full:string

1 .. SPDX-License-Identifier: GPL-2.0
19 ------------
21 The NFSv4 protocol uses "lease-based file locking". Leases help
48 ------------------------
54   - co_ownerid: An arbitrary but fixed string.
56   - boot verifier: A 64-bit incarnation verifier that enables a
70 "co_ownerid" string has several important properties:
72   - The "co_ownerid" string identifies the client during reboot
73     recovery, therefore the string is persistent across client
75   - The "co_ownerid" string helps servers distinguish the client
76     from others, therefore the string is globally unique. Note
79   - Because it often appears on the network in the clear, the
80     "co_ownerid" string does not reveal private information about
82   - The content of the "co_ownerid" string is set and unchanging
84   - The NFSv4 protocol places a 1024-byte limit on the size of the
85     "co_ownerid" string.
88 ----------------------------
95 If distinct clients present the same "co_ownerid" string and use
102 If distinct clients present the same "co_ownerid" string and use
105 "co_ownerid" string.
107 If a client's "co_ownerid" string or principal are not stable,
110 "co_ownerid" string or principal to the server, the server orphans
115 string or principal to the server, the server will not allow the
124 ------------------------------------------
127 "co_ownerid" string starting with the words "Linux NFS" followed by
134   - NFS-root (diskless) clients, where the local DHCP server (or
137   - "Containers" within a single Linux host.  If each container has
142   - Clients across multiple administrative domains that access a
148 string:
151       This module parameter can set an arbitrary uniquifier string
161 Note that this file is empty on name-space creation. If the
162 container system has access to some sort of per-container identity
166     sha256sum /etc/machine-id | awk '{print $1}' \\
170 -----------------------
180 "co_ownerid" string uniqueness and persistence is critical in this
186 control this behavior. Alternately, a single-user client with a
193 flavor with Kerberos and the integrity QOS to prevent in-transit
197 ----------------
213   - nfs(5)
214   - kerberos(7)
215   - RFC 7530 for the NFSv4.0 specification
216   - RFC 8881 for the NFSv4.1 specification.