From: Sheng Yong <shengyong1@huawei.com>
To: <dedekind1@gmail.com>, <richard.weinberger@gmail.com>,
<andreas.gruenbacher@gmail.com>
Cc: <linux-mtd@lists.infradead.org>, <yangds.fnst@cn.fujitsu.com>,
<linux-fsdevel@vger.kernel.org>
Subject: [RFC PATCH v3 0/5] UBIFS: add ACL support
Date: Fri, 11 Sep 2015 09:09:52 +0000 [thread overview]
Message-ID: <1441962597-13543-1-git-send-email-shengyong1@huawei.com> (raw)
Hi, folks,
These patches add ACL support for UBIFS.
UBIFS ACL is based on xattr, which simplifies the implementation without
considering budget and sync.
New kernel/mount options, CONFIG_UBIFS_FS_POSIX_ACL and `-o acl', are
introduced to enable or disable UBIFS ACL.
`acl.c' provides format conversion between in-memory ACL and on-flash ACL.
Each time a new inode is created, the correspondng ACL xattr is built
(except for the inode of an xattr dent).
Testcases (adjusted to mount an UBI volume) in LTP [1] are passed.
Any comment is appreciated. More test is appreciated.
V3:
* Use POSIX generic ACL structures and functions to do the conversions
between in-memory and on-flash ACL. Thanks Dongsheng Yang for pointing
this out.
* Remove ACL if size is 0 when setting ACL.
* Clear cached ACL when ACL xattr is removed.
V2:
* Do not set ACL-xattr-handler, and call generic ACL handler in xattr
functions.
http://lists.infradead.org/pipermail/linux-mtd/2015-September/061672.html
V1:
http://lists.infradead.org/pipermail/linux-mtd/2015-March/058452.html
[1] https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/fs/acl/tacl_xattr.sh
thanks,
Sheng
Sheng Yong (5):
UBIFS: ACL: introduce init/set/get functions for ACL
UBIFS: ACL: set ACL interfaces in inode_operations
UBIFS: ACL: handle ACL through xattr
UBIFS: ACL: introduce ACL mount options
UBIFS: ACL: add ACL config option
fs/ubifs/Kconfig | 11 +++
fs/ubifs/Makefile | 1 +
fs/ubifs/acl.c | 141 +++++++++++++++++++++++++++++++
fs/ubifs/dir.c | 20 +++++
fs/ubifs/file.c | 14 ++++
fs/ubifs/super.c | 15 ++++
fs/ubifs/ubifs.h | 14 ++++
fs/ubifs/xattr.c | 243 ++++++++++++++++++++++++++++++++++--------------------
8 files changed, 369 insertions(+), 90 deletions(-)
create mode 100644 fs/ubifs/acl.c
--
1.9.1
next reply other threads:[~2015-09-11 1:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 9:09 Sheng Yong [this message]
2015-09-11 9:09 ` [RFC PATCH v3 1/5] UBIFS: ACL: introduce init/set/get functions for ACL Sheng Yong
2015-09-11 5:01 ` Dongsheng Yang
2015-09-11 6:13 ` Sheng Yong
2015-09-11 6:21 ` Dongsheng Yang
2015-09-11 20:05 ` Andreas Grünbacher
2015-09-11 9:09 ` [RFC PATCH v3 2/5] UBIFS: ACL: set ACL interfaces in inode_operations Sheng Yong
2015-09-11 9:09 ` [RFC PATCH v3 3/5] UBIFS: ACL: handle ACL through xattr Sheng Yong
2015-09-11 5:01 ` Dongsheng Yang
2015-09-11 6:18 ` Sheng Yong
2015-09-11 6:25 ` Dongsheng Yang
2015-09-12 1:15 ` Sheng Yong
2015-09-14 0:39 ` Dongsheng Yang
2015-09-11 9:09 ` [RFC PATCH v3 4/5] UBIFS: ACL: introduce ACL mount options Sheng Yong
2015-09-11 5:03 ` Dongsheng Yang
2015-09-11 8:25 ` Sheng Yong
2015-09-11 8:25 ` Dongsheng Yang
2015-09-11 9:09 ` [RFC PATCH v3 5/5] UBIFS: ACL: add ACL config option Sheng Yong
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=1441962597-13543-1-git-send-email-shengyong1@huawei.com \
--to=shengyong1@huawei.com \
--cc=andreas.gruenbacher@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
--cc=yangds.fnst@cn.fujitsu.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).