From: Satya Tangirala <satyat@google.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Eric Biggers <ebiggers@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org,
Satya Tangirala <satyat@google.com>
Subject: [PATCH 0/1] userspace support for F2FS metadata encryption
Date: Mon, 5 Oct 2020 07:41:32 +0000 [thread overview]
Message-ID: <20201005074133.1958633-1-satyat@google.com> (raw)
The kernel patches for F2FS metadata encryption are at:
https://lore.kernel.org/linux-fscrypt/20201005073606.1949772-4-satyat@google.com/
This patch implements the userspace changes required for metadata
encryption support as implemented in the kernel changes above. All blocks
in the filesystem are encrypted with the user provided metadata encryption
key except for the superblock (and its redundant copy). The DUN for a block
is its offset from the start of the filesystem.
This patch introduces two new options for the userspace tools: '-A' to
specify the encryption algorithm, and '-M' to specify the encryption key.
mkfs.f2fs will store the encryption algorithm used for metadata encryption
in the superblock itself, so '-A' is only applicable to mkfs.f2fs. The rest
of the tools only take the '-M' option, and will obtain the encryption
algorithm from the superblock of the FS.
Limitations:
Metadata encryption with sparse storage has not been implemented yet in
this patch.
This patch requires the metadata encryption key to be readable from
userspace, and does not ensure that it is zeroed before the program exits
for any reason.
Satya Tangirala (1):
f2fs-tools: Introduce metadata encryption support
fsck/main.c | 47 ++++++-
fsck/mount.c | 33 ++++-
include/f2fs_fs.h | 10 +-
include/f2fs_metadata_crypt.h | 21 ++++
lib/Makefile.am | 4 +-
lib/f2fs_metadata_crypt.c | 226 ++++++++++++++++++++++++++++++++++
lib/libf2fs_io.c | 87 +++++++++++--
mkfs/f2fs_format.c | 5 +-
mkfs/f2fs_format_main.c | 33 ++++-
9 files changed, 446 insertions(+), 20 deletions(-)
create mode 100644 include/f2fs_metadata_crypt.h
create mode 100644 lib/f2fs_metadata_crypt.c
--
2.28.0.806.g8561365e88-goog
next reply other threads:[~2020-10-05 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 7:41 Satya Tangirala [this message]
2020-10-05 7:41 ` [PATCH 1/1] f2fs-tools: Introduce metadata encryption support Satya Tangirala
2020-10-07 19:42 ` jaegeuk
2020-12-17 16:04 ` Satya Tangirala
2020-10-07 21:52 ` Eric Biggers
2020-10-07 21:39 ` [PATCH 0/1] userspace support for F2FS metadata encryption Eric Biggers
2020-12-17 16:23 ` Jaegeuk Kim
2020-12-18 6:41 ` Satya Tangirala
2020-12-18 16:19 ` 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=20201005074133.1958633-1-satyat@google.com \
--to=satyat@google.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--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).