Skip to content

Commit 3e2a036

Browse files
DaveWysochanskiRHamschuma-ntap
authored andcommitted
Documentation: Fix sysfs path for the NFSv4 client identifier
The sysfs path for the NFS4 client identfier should start with the path component of 'nfs' for the kset, and then the 'net' path component for the netns object, followed by the 'nfs_client' path component for the NFS client kobject, and ending with 'identifier' for the netns_client_id kobj_attribute. Fixes: a28faad ("Documentation: Add an explanation of NFSv4 client identifiers") Link: https://bugzilla.redhat.com/show_bug.cgi?id=1801326 Reviewed-by: Chuck Lever <[email protected]> Signed-off-by: Dave Wysochanski <[email protected]> Signed-off-by: Anna Schumaker <[email protected]>
1 parent 4730515 commit 3e2a036

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Documentation/filesystems/nfs/client-identifier.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,7 @@ string:
152152
via the kernel command line, or when the "nfs" module is
153153
loaded.
154154

155-
/sys/fs/nfs/client/net/identifier
155+
/sys/fs/nfs/net/nfs_client/identifier
156156
This virtual file, available since Linux 5.3, is local to the
157157
network namespace in which it is accessed and so can provide
158158
distinction between network namespaces (containers) when the
@@ -164,7 +164,7 @@ then that uniquifier can be used. For example, a uniquifier might
164164
be formed at boot using the container's internal identifier:
165165

166166
sha256sum /etc/machine-id | awk '{print $1}' \\
167-
> /sys/fs/nfs/client/net/identifier
167+
> /sys/fs/nfs/net/nfs_client/identifier
168168

169169
Security considerations
170170
-----------------------

0 commit comments

Comments
 (0)