File 0001-cifs-utils-add-documentation-for-upcall_target.patch of Package cifs-utils.41102
From cf63240489431e98033e599a7c9437b59494a2e4 Mon Sep 17 00:00:00 2001 From: Ritvik Budhiraja <rbudhiraja@microsoft.com> Date: Thu, 30 Jan 2025 14:13:10 +0000 Subject: [PATCH] cifs-utils: add documentation for upcall_target Update man page with documentation for upcal_target mount parameter. Signed-off-by: Ritvik Budhiraja <rbudhiraja@microsoft.com> Signed-off-by: Steve French <stfrench@microsoft.com> Signed-off-by: Henrique Carvalho <henrique.carvalho@suse.com> --- mount.cifs.rst | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) --- a/mount.cifs.rst +++ b/mount.cifs.rst @@ -348,7 +348,7 @@ an argument, there are no default values. See section `ACCESSING FILES WITH BACKUP INTENT`_ for more details. - + nocase Request case insensitive path name matching (case sensitive is the default if the server supports it). @@ -380,6 +380,21 @@ Request encryption at the SMB layer. The encryption algorithm used is AES-128-CCM. Requires SMB3 or above (see ``vers``). +upcall_target=arg + Determines the namespace in which upcalls from the SMB filesystem should be handled. + Allowed values are: + - ``mount`` - Resolve upcalls to the host namespace. + - ``app`` - Resolve upcalls in the namespace of the calling thread (application). + Default value is ``app``. + This option is useful in environments like Kubernetes, where the mount + may be performed by a driver pod on behalf of an application running + in a separate container. It ensures that Kerberos credentials and other + user-specific data are accessed in the correct namespace. + By specifying ``app``, upcalls can be resolved in the application's namespace, + ensuring the correct credentials are used. ``mount`` allows resolution in the + host namespace, which may be necessary when credentials or configurations + are managed outside the container. + rdma Connect directly to the server using SMB Direct via a RDMA adapter. Requires SMB3 or above (see ``vers``).
