Linux-CIFS Archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: Paulo Alcantara <pc@manguebit.com>
Cc: piastryyy@gmail.com, linux-cifs@vger.kernel.org
Subject: Re: [PATCH 1/2] mount.cifs.rst: add missing reference for sssd
Date: Mon, 11 Mar 2024 09:41:07 -0500	[thread overview]
Message-ID: <CAH2r5mt+kcWu4jFwKfn4izwhFxCbGNDaAbR7ReKfX3cxdQoidg@mail.gmail.com> (raw)
In-Reply-To: <20240311012425.156879-1-pc@manguebit.com>

You can add
Reviewed-by: Steve French <stfrench@microsoft.com>

On Sun, Mar 10, 2024 at 8:24 PM Paulo Alcantara <pc@manguebit.com> wrote:
>
> Reference sssd in mount.cifs(8) as it can be used instead of winbind
> via cifs.idmap utility.  It's also enabled by default in most systems.
>
> Signed-off-by: Paulo Alcantara (Red Hat) <pc@manguebit.com>
> ---
>  mount.cifs.rst | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/mount.cifs.rst b/mount.cifs.rst
> index 9d4446f035b6..f0ddef97a0e8 100644
> --- a/mount.cifs.rst
> +++ b/mount.cifs.rst
> @@ -761,10 +761,10 @@ specified in the following Microsoft TechNet document:
>  In order to map SIDs to/from UIDs and GIDs, the following is required:
>
>  - a kernel upcall to the ``cifs.idmap`` utility set up via request-key.conf(5)
> -- winbind support configured via nsswitch.conf(5) and smb.conf(5)
> +- winbind or sssd support configured via nsswitch.conf(5)
>
> -Please refer to the respective manpages of cifs.idmap(8) and
> -winbindd(8) for more information.
> +Please refer to the respective manpages of cifs.idmap(8), winbindd(8)
> +and sssd(8) for more information.
>
>  Security descriptors for a file object can be retrieved and set
>  directly using extended attribute named ``system.cifs_acl``. The
> @@ -780,10 +780,10 @@ Some of the things to consider while using this mount option:
>  - The mapping between a CIFS/NTFS ACL and POSIX file permission bits
>    is imperfect and some ACL information may be lost in the
>    translation.
> -- If either upcall to cifs.idmap is not setup correctly or winbind is
> -  not configured and running, ID mapping will fail. In that case uid
> -  and gid will default to either to those values of the share or to
> -  the values of uid and/or gid mount options if specified.
> +- If either upcall to cifs.idmap is not setup correctly or winbind or
> +  sssd is not configured and running, ID mapping will fail. In that
> +  case uid and gid will default to either to those values of the share
> +  or to the values of uid and/or gid mount options if specified.
>
>  **********************************
>  ACCESSING FILES WITH BACKUP INTENT
> --
> 2.44.0
>
>


-- 
Thanks,

Steve

      parent reply	other threads:[~2024-03-11 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11  1:24 [PATCH 1/2] mount.cifs.rst: add missing reference for sssd Paulo Alcantara
2024-03-11  1:24 ` [PATCH 2/2] mount.cifs.rst: update section about xattr/acl support Paulo Alcantara
2024-03-11 14:39   ` Steve French
2024-03-11 14:41 ` Steve French [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAH2r5mt+kcWu4jFwKfn4izwhFxCbGNDaAbR7ReKfX3cxdQoidg@mail.gmail.com \
    --to=smfrench@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pc@manguebit.com \
    --cc=piastryyy@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).