From: ronnie sahlberg <ronniesahlberg@gmail.com>
To: Jacob Shivers <jshivers@redhat.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: cruid+multiuser mount options
Date: Fri, 17 Jan 2020 05:20:57 +1000 [thread overview]
Message-ID: <CAN05THRzWK_3g+Eyt_dFThEyu6ejNwBPEFE+JzG8b0SOj7pY7A@mail.gmail.com> (raw)
In-Reply-To: <CALe0_75KJMBOMMAtSWNH=GkHv-vzvYQxOVuj8Eht6jfVfoYCcA@mail.gmail.com>
On Fri, Jan 17, 2020 at 3:57 AM Jacob Shivers <jshivers@redhat.com> wrote:
>
> When mounting a Kerberized SMB share with both cruid and multiuser,
> the multiuser mount option is negated. This is not documented as
> explicit behavior. The question is whether this intended behavior or
> if it is unexpected.
>
> Does anyone have any existing thoughts on this?
To me it does not make sense to allow cruid and multiuser at the same time.
I think we should
1, document they are mutually exclusive
2, check for this and fail the mount with a log message if both
options are used concurrently.
>
next prev parent reply other threads:[~2020-01-16 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 17:56 cruid+multiuser mount options Jacob Shivers
2020-01-16 19:20 ` ronnie sahlberg [this message]
2020-01-17 6:28 ` Steve French
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=CAN05THRzWK_3g+Eyt_dFThEyu6ejNwBPEFE+JzG8b0SOj7pY7A@mail.gmail.com \
--to=ronniesahlberg@gmail.com \
--cc=jshivers@redhat.com \
--cc=linux-cifs@vger.kernel.org \
/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 NNTP newsgroup(s).