| Message ID | CA+EPQ647ii+vEbiaYT5dQXn__t2KEVypKyfsovbrwCrBQcTZow@mail.gmail.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | cifs-utils: add documentation for upcall_target | expand |
Have updated cifs-utils for-next with this (after cleaning up some minor whitespace warnings) Currently have the following 16 patches in cifs-utils. Let me know if any objections. /cifs-utils$ git log --oneline -17 --no-merges cf63240 (HEAD -> for-next) cifs-utils: add documentation for upcall_target f6fddc4 (origin/for-next) cifs-utils: avoid using mktemp when updating mtab 5e80978 cldap_ping.c: add missing <sys/types.h> include 119f7bf configure.ac: libtalloc is now mandatory 1561527 cifscreds: allow user to set the key's timeout f9d2e82 (tmp1) cifscreds: use continue instead of break when matching commands 974249d Do not pass passwords with sec=none and sec=krb5 71103eb docs: add esize description 4882c91 docs: add max_cached_dirs description a241032 docs: update actimeo description 3b39843 Fix compiler warnings in mount.cifs 89b6792 CIFS.upcall to accomodate new namespace mount opt af76bf2 cifs-utils: Skip TGT check if valid service ticket is already available a8252db use enums to check password or password2 in set_password, get_password_from_file and minor documentation additions e447a48 cifs-utils: support and document password2 mount option 6cf2f47 smbinfo: add bash completion support for filestreaminfo, keys, gettconinfo 0fae4c7 (tag: cifs-utils-7.1, origin/master, origin/HEAD, master) cifs-utils: bump version to 7.1 On Thu, Jan 30, 2025 at 8:43 AM Ritvik Budhiraja <budhirajaritviksmb@gmail.com> wrote: > > From: Ritvik Budhiraja <rbudhiraja@microsoft.com> > > Update man page with documentation for upcal_target > mount parameter. > > Signed-off-by: Ritvik Budhiraja <rbudhiraja@microsoft.com> > --- > mount.cifs.rst | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > > diff --git a/mount.cifs.rst b/mount.cifs.rst > index 67c5138..631482d 100644 > --- a/mount.cifs.rst > +++ b/mount.cifs.rst > @@ -636,6 +636,21 @@ acdirmax=arg > If this option is not specified, then acdirmax value will be set to > ``actimeo`` > value, see ``actimeo`` for more details. > > +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. > + > multichannel > This option enables multichannel feature. Multichannel is an SMB3 protocol > feature that allows client to establish multiple transport connections to an > -- > 2.43.0 >
diff --git a/mount.cifs.rst b/mount.cifs.rst index 67c5138..631482d 100644 --- a/mount.cifs.rst +++ b/mount.cifs.rst @@ -636,6 +636,21 @@ acdirmax=arg If this option is not specified, then acdirmax value will be set to ``actimeo`` value, see ``actimeo`` for more details. +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.