Linux-mtd Archive mirror
 help / color / mirror / Atom feed
From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Li Zetao <lizetao1@huawei.com>, <richard@nod.at>,
	<corbet@lwn.net>, <kent.overstreet@linux.dev>,
	<agruenba@redhat.com>
Cc: <linux-mtd@lists.infradead.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2 5/5] ubifs: Introduce ACLs mount options
Date: Sat, 23 Mar 2024 10:55:26 +0800	[thread overview]
Message-ID: <e10b4182-a6b6-25f5-b04d-92bc20fa56d4@huawei.com> (raw)
In-Reply-To: <20240322154812.215369-6-lizetao1@huawei.com>

在 2024/3/22 23:48, Li Zetao 写道:
> Implement the ability to enable or disable the ACLs feature through
> mount options. "-o acl" option means enable and "-o noacl" means disable
> and it is enable by default.
> 
> Signed-off-by: Li Zetao <lizetao1@huawei.com>
> ---
> v1 -> v2:
>    * Remove redundant assignments to mount.acl.
>    * Added the description of acl mount options in ubifs.rst.
> 
> v1: https://lore.kernel.org/all/20240319161646.2153867-5-lizetao1@huawei.com/
> 
>   Documentation/filesystems/ubifs.rst |  4 +++
>   fs/ubifs/super.c                    | 41 +++++++++++++++++++++++++++++
>   fs/ubifs/ubifs.h                    |  2 ++
>   3 files changed, 47 insertions(+)
> 
> diff --git a/Documentation/filesystems/ubifs.rst b/Documentation/filesystems/ubifs.rst
> index ced2f7679ddb..f9615104d7a3 100644
> --- a/Documentation/filesystems/ubifs.rst
> +++ b/Documentation/filesystems/ubifs.rst
> @@ -105,6 +105,10 @@ auth_key=		specify the key used for authenticating the filesystem.
>   auth_hash_name=		The hash algorithm used for authentication. Used for
>   			both hashing and for creating HMACs. Typical values
>   			include "sha256" or "sha512"
> +noacl			This option disables POSIX Access Control List support. If ACL support
> +			is enabled in the kernel configuration (CONFIG_EXT4_FS_POSIX_ACL), ACL
> +			is enabled by default on mount. See the acl(5) manual page for more
> +			information about acl.
Also add acl description?
Split documentation into a new patch?

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2024-03-23  2:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 15:48 [RFC PATCH v2 0/5] ubifs: Support POSIX Access Control Lists (ACLs) Li Zetao
2024-03-22 15:48 ` [RFC PATCH v2 1/5] ubifs: Add ACLs config option Li Zetao
2024-03-22 15:48 ` [RFC PATCH v2 2/5] ubifs: Implement POSIX Access Control Lists (ACLs) Li Zetao
2024-03-23  2:42   ` Zhihao Cheng
2024-03-22 15:48 ` [RFC PATCH v2 3/5] ubifs: Initialize or update ACLs for inode Li Zetao
2024-03-22 15:48 ` [RFC PATCH v2 4/5] ubifs: Support accessing ACLs through inode_operations Li Zetao
2024-03-22 15:48 ` [RFC PATCH v2 5/5] ubifs: Introduce ACLs mount options Li Zetao
2024-03-23  2:55   ` Zhihao Cheng [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=e10b4182-a6b6-25f5-b04d-92bc20fa56d4@huawei.com \
    --to=chengzhihao1@huawei.com \
    --cc=agruenba@redhat.com \
    --cc=corbet@lwn.net \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lizetao1@huawei.com \
    --cc=richard@nod.at \
    /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).