From: Eric Biggers <ebiggers@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: linux-fscrypt@vger.kernel.org,
Daniel Rosenberg <drosen@google.com>,
Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: [PATCH 0/4] f2fs: rework filename handling
Date: Thu, 7 May 2020 00:59:01 -0700 [thread overview]
Message-ID: <20200507075905.953777-1-ebiggers@kernel.org> (raw)
This patchset reworks f2fs's handling of filenames to make it much
easier to correctly implement all combinations of normal, encrypted,
casefolded, and encrypted+casefolded directories. It also optimizes all
filesystem operations to compute the dirhash and casefolded name only
once, rather than once per directory level or directory block.
Patch 4 is RFC and shows how we can add support for encrypted+casefolded
directories fairly easily after this rework -- including support for
roll-forward recovery. (It's incomplete as it doesn't include the
needed dentry_ops -- those can be found in Daniel's patchset
https://lkml.kernel.org/r/20200307023611.204708-1-drosen@google.com)
So far this is only lightly tested, e.g. with the xfstests in the
'encrypt' and 'casefold' groups. I haven't tested patch 4 yet.
Eric Biggers (4):
f2fs: don't leak filename in f2fs_try_convert_inline_dir()
f2fs: split f2fs_d_compare() from f2fs_match_name()
f2fs: rework filename handling
f2fs: Handle casefolding with Encryption (INCOMPLETE)
fs/f2fs/dir.c | 415 +++++++++++++++++++++++++++------------------
fs/f2fs/f2fs.h | 85 +++++++---
fs/f2fs/hash.c | 87 +++++-----
fs/f2fs/inline.c | 49 +++---
fs/f2fs/namei.c | 6 +-
fs/f2fs/recovery.c | 61 +++++--
6 files changed, 430 insertions(+), 273 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-07 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 7:59 Eric Biggers [this message]
2020-05-07 7:59 ` [PATCH 1/4] f2fs: don't leak filename in f2fs_try_convert_inline_dir() Eric Biggers
2020-05-08 8:25 ` Chao Yu
2020-05-07 7:59 ` [PATCH 2/4] f2fs: split f2fs_d_compare() from f2fs_match_name() Eric Biggers
2020-05-11 2:47 ` Chao Yu
2020-05-07 7:59 ` [PATCH 3/4] f2fs: rework filename handling Eric Biggers
2020-05-25 8:12 ` Chao Yu
2020-05-25 15:10 ` [f2fs-dev] " Jaegeuk Kim
2020-05-07 7:59 ` [RFC PATCH 4/4] f2fs: Handle casefolding with Encryption (INCOMPLETE) Eric Biggers
2020-05-08 2:55 ` Eric Biggers
2020-05-07 13:09 ` [f2fs-dev] [PATCH 0/4] f2fs: rework filename handling Jaegeuk Kim
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=20200507075905.953777-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=drosen@google.com \
--cc=krisman@collabora.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
/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).