From: Shyam Prasad N <nspmangalore@gmail.com>
To: Steve French <smfrench@gmail.com>, CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH] cifs: use both modefromsid and idsfromsid when either one is specified
Date: Thu, 5 Aug 2021 10:22:37 +0530 [thread overview]
Message-ID: <CANT5p=pxO0W7tt5tMLhq_VneO3yZ_Ou2HmjDyYrhB3p8aYDZfg@mail.gmail.com> (raw)
In-Reply-To: <CANT5p=oFC6ekqPQxmE5Hx6511ge3Bi0xjQn2abPdbKTo_j6JxA@mail.gmail.com>
Please ignore this patch. I'll be sending the correct fix as another patch.
On Wed, Aug 4, 2021 at 6:21 PM Shyam Prasad N <nspmangalore@gmail.com> wrote:
>
> Hi Steve,
>
> Please review the fix for the bug reported at:
> https://bugzilla.kernel.org/show_bug.cgi?id=213927
>
> We don't have a way today not to set particular fields in a security descriptor on create. We need to supply the whole SD. We could do a getinfo followed by setinfo, but that's more complicated, and is prone to race conditions.
>
> https://github.com/sprasad-microsoft/smb3-kernel-client/pull/3
>
> --
> Regards,
> Shyam
--
Regards,
Shyam
parent reply other threads:[~2021-08-05 4:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CANT5p=oFC6ekqPQxmE5Hx6511ge3Bi0xjQn2abPdbKTo_j6JxA@mail.gmail.com>]
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='CANT5p=pxO0W7tt5tMLhq_VneO3yZ_Ou2HmjDyYrhB3p8aYDZfg@mail.gmail.com' \
--to=nspmangalore@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=smfrench@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 NNTP newsgroup(s).