From: "Björn JACKE" <bj@SerNet.DE>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-cifs@vger.kernel.org
Subject: Re: we actually need richacls ...
Date: Thu, 18 Mar 2021 08:50:25 +0100 [thread overview]
Message-ID: <20210318075025.GA600594@sernet.de> (raw)
In-Reply-To: <bug-14494-10630-dugIJZXmUw@https.bugzilla.samba.org/>
On 2021-03-18 at 07:33 +0000 samba-bugs@samba.org sent off:
> --- Comment #1 from Björn Jacke <bjacke@samba.org> ---
> Generlly much of the cifsacl stuff is really nice bug with the outstanding
> bugs, some of those that Micah reported, cifs vfs with NT ACLs is just not
> usable and people who *need* to use full NT ACLs with a POSIX client have no
> other option than using a different OS with native NFS4 ACLs support like
> FreeBSD currently.
it would also be great if the cifs developers would all trogether try to
convince the kernel developers that the richacl implmentation gets upstreamed.
cifs vfs urgently needs it. NT ACLs on POSIX clients are practically unusabe
without having richalcs. Same for the upcoming cifs kernel server.
I tried to bring up the richacl topic a while ago on the kerenel mailing list
but the voices of many of the cifs developers will be much more significant and
can not so easily be ignored by the kernel maintainer I think.
Björn
next prev parent reply other threads:[~2021-03-18 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 2:14 [Bug 14494] New: "setcifsacl" confuses "R" permission with "RX" samba-bugs
2021-03-18 7:33 ` [Bug 14494] " samba-bugs
2021-03-18 7:50 ` Björn JACKE [this message]
[not found] ` <CAH2r5msva0XmGjNMonOp0PtXXi5aJeAZ92Cr_MeohEwhzK-kWQ@mail.gmail.com>
[not found] ` <CAN05THTtitSbSEbXtFDJUB3dpTzBFEh5bQLSE=mSheLrsvvNrA@mail.gmail.com>
2021-03-22 11:30 ` we actually need richacls Björn JACKE
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=20210318075025.GA600594@sernet.de \
--to=bj@sernet.de \
--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).