From: Sheng Yong <shengyong1@huawei.com>
To: <dedekind1@gmail.com>, <adrian.hunter@intel.com>
Cc: miaoxie@huawei.com, linux-mtd@lists.infradead.org, hujianyang@huawei.com
Subject: [RFC PATCH 0/3] UBIFS: add ACL support
Date: Wed, 25 Mar 2015 11:46:02 +0000 [thread overview]
Message-ID: <1427283965-86137-1-git-send-email-shengyong1@huawei.com> (raw)
UBIFS ACL is based on xattr. Three structures, ubifs_acl_header,
ubifs_acl_entry, and ubifs_acl_entry_short are used to format the ACL
value on flash.
ACL format between in-memory and on-flash is switched before writting
it to flash and after reading it from flash. The writting and reading
operations are implemented by generic set/get xattr functions. ACL of
a new file is inheritted from the parent directory when creating new
inode.
For xattr, generic functions of setting and getting xattr are splited
from original ubifs_setxattr and ubifs_getxattr so that ACL could use
them.
Thanks,
Sheng
Sheng Yong (3):
UBIFS: xattr: splite generic set/get xattr functions from
ubifs_set/getxattr
UBIFS: ACL: add ACL support
UBIFS: ACL: add ACL config option
fs/ubifs/Kconfig | 11 ++
fs/ubifs/Makefile | 1 +
fs/ubifs/acl.c | 316 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
fs/ubifs/dir.c | 7 ++
fs/ubifs/file.c | 14 +++
fs/ubifs/super.c | 15 +++
fs/ubifs/ubifs.h | 7 ++
fs/ubifs/xattr.c | 52 +++++++--
8 files changed, 413 insertions(+), 10 deletions(-)
create mode 100644 fs/ubifs/acl.c
--
1.8.3.4
next reply other threads:[~2015-03-25 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 11:46 Sheng Yong [this message]
2015-03-25 11:46 ` [RFC PATCH 1/3] UBIFS: xattr: splite generic set/get xattr functions from ubifs_set/getxattr Sheng Yong
2015-03-25 11:46 ` [RFC PATCH 2/3] UBIFS: ACL: add ACL support Sheng Yong
2015-04-07 1:14 ` Sheng Yong
2015-03-25 11:46 ` [RFC PATCH 3/3] 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=1427283965-86137-1-git-send-email-shengyong1@huawei.com \
--to=shengyong1@huawei.com \
--cc=adrian.hunter@intel.com \
--cc=dedekind1@gmail.com \
--cc=hujianyang@huawei.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miaoxie@huawei.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).