Commit 3e2a0368 authored Jan 23, 2023 by Dave Wysochanski Committed by Anna Schumaker Feb 15, 2023

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: a28faadd ("Documentation: Add an explanation of NFSv4 client identifiers")
Link: https://bugzilla.redhat.com/show_bug.cgi?id=1801326


Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

parent 47305153

Documentation/filesystems/nfs/client-identifier.rst

+2 −2

Original line number	Diff line number	Diff line
		@@ -152,7 +152,7 @@ string:
		via the kernel command line, or when the "nfs" module is
		loaded.

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

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

		Security considerations
		-----------------------