From: Sheng Yong <shengyong1@huawei.com>
To: jaegeuk@kernel.org, yuchao0@huawei.com, ebiggers@google.com,
tytso@mit.edu
Cc: linux-fscrypt@vger.kernel.org, miaoxie@huawei.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: [RFC PATCH v5 0/3] f2fs: introduce F2FS_FEATURE_LOST_FOUND feature
Date: Thu, 15 Mar 2018 18:51:40 +0800 [thread overview]
Message-ID: <20180315105143.133050-1-shengyong1@huawei.com> (raw)
v5->v4:
* add doc for new mount option test_dummy_encryption
* move test_dummy_encryption flag to f2fs_mount_info
* move DUMMY_ENCRYPTION_ENABLED check to parse_option
* remove readonly check since we don't enable encrypt feature forcely
v4->v3:
* split f2fs patch into 2: one for LOST_FOUND feature, another for
test_dummy_encryption
* do not set enc_name if dir is not encrypted
* do not allow mounting with test_dummy_encryption if encrypt feature
is not set
v3->v2:
* fix test_dummy_encryption
v2->v1:
* introduce new mount option test_dummy_encryption
* add sysfs entry for LOST_FOUND feature
---8<---
This patchset introduces LOST_FOUND feature in f2fs. If the feature is
enabled, f2fs should avoid to encrypt root directory.
A new mount option "test_dummy_encryption" is introduced, this is used by
xfstests.
Thanks,
Sheng
Sheng Yong (3):
f2fs: introduce F2FS_FEATURE_LOST_FOUND feature
f2fs: introduce a new mount option test_dummy_encryption
ext4: do not allow mount with test_dummy_encryption if encrypt not set
Documentation/filesystems/f2fs.txt | 2 ++
fs/ext4/super.c | 7 +++----
fs/f2fs/dir.c | 4 +++-
fs/f2fs/f2fs.h | 10 ++++++++++
fs/f2fs/namei.c | 9 ++++++---
fs/f2fs/super.c | 40 ++++++++++++++++++++++++++++++++++++++
fs/f2fs/sysfs.c | 7 +++++++
7 files changed, 71 insertions(+), 8 deletions(-)
--
2.16.2
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next reply other threads:[~2018-03-15 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 10:51 Sheng Yong [this message]
2018-03-15 10:51 ` [RFC PATCH v5 1/3] f2fs: introduce F2FS_FEATURE_LOST_FOUND feature Sheng Yong
2018-03-15 10:51 ` [RFC PATCH v5 2/3] f2fs: introduce a new mount option test_dummy_encryption Sheng Yong
2018-03-16 8:49 ` Chao Yu
2018-03-15 10:51 ` [RFC PATCH v5 3/3] ext4: do not allow mount with test_dummy_encryption if encrypt not set 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=20180315105143.133050-1-shengyong1@huawei.com \
--to=shengyong1@huawei.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=tytso@mit.edu \
--cc=yuchao0@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).