From: Chao Yu <chao@kernel.org>
To: Sheng Yong <shengyong1@huawei.com>,
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: Re: [RFC PATCH v4 1/3] f2fs: introduce F2FS_FEATURE_LOST_FOUND feature
Date: Fri, 9 Mar 2018 20:31:47 +0800 [thread overview]
Message-ID: <3b87131c-7c8e-0904-f46c-36de2b3d4d3d@kernel.org> (raw)
In-Reply-To: <20180309075312.62357-2-shengyong1@huawei.com>
On 2018/3/9 15:53, Sheng Yong wrote:
> This patch introduces a new feature, F2FS_FEATURE_LOST_FOUND, which
> is set by mkfs. mkfs creates a directory named lost+found, which saves
> unreachable files. If fsck finds a file which has no parent, or its
> parent is removed by fsck, the file will be placed under lost+found
> directory by fsck.
>
> lost+found directory could not be encrypted. As a result, the root
> directory cannot be encrypted too. So if LOST_FOUND feature is enabled,
> let's avoid to encrypt root directory.
>
> Signed-off-by: Sheng Yong <shengyong1@huawei.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-03-09 12:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 7:53 [RFC PATCH v4 0/3] f2fs: introduce F2FS_FEATURE_LOST_FOUND feature Sheng Yong
2018-03-09 7:53 ` [RFC PATCH v4 1/3] " Sheng Yong
2018-03-09 12:31 ` Chao Yu [this message]
2018-03-09 7:53 ` [RFC PATCH v4 2/3] f2fs: introduce a new mount option test_dummy_encryption Sheng Yong
2018-03-09 12:32 ` Chao Yu
2018-03-12 1:13 ` Sheng Yong
2018-03-09 7:53 ` [RFC PATCH 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=3b87131c-7c8e-0904-f46c-36de2b3d4d3d@kernel.org \
--to=chao@kernel.org \
--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=shengyong1@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).