From: Eric Biggers <ebiggers@kernel.org>
To: linux-block@vger.kernel.org, linux-fscrypt@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, kernel-team@android.com,
Thara Gopinath <thara.gopinath@linaro.org>,
Gaurav Kashyap <gaurkash@codeaurora.org>,
Satya Tangirala <satyaprateek2357@gmail.com>
Subject: Re: [RFC PATCH v2 3/5] fscrypt: improve documentation for inline encryption
Date: Mon, 20 Sep 2021 20:13:49 -0700 [thread overview]
Message-ID: <YUlN7TY7z5/2EcFF@sol.localdomain> (raw)
In-Reply-To: <20210916174928.65529-4-ebiggers@kernel.org>
On Thu, Sep 16, 2021 at 10:49:26AM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Currently the fscrypt inline encryption support is documented in the
> "Implementation details" section, and it doesn't go into much detail.
> It's really more than just an "implementation detail" though, as there
> is a user-facing mount option. Also, hardware-wrapped key support (an
> upcoming feature) will depend on inline encryption and will affect the
> on-disk format; by definition that's not just an implementation detail.
>
> Therefore, move this documentation into its own section and expand it.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> Documentation/block/inline-encryption.rst | 2 +
> Documentation/filesystems/fscrypt.rst | 73 +++++++++++++++++------
> 2 files changed, 58 insertions(+), 17 deletions(-)
I've applied this patch to fscrypt.git#master for 5.16, as it's a useful cleanup
which isn't dependent on the hardware-wrapped keys feature.
- Eric
next prev parent reply other threads:[~2021-09-21 3:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 17:49 [RFC PATCH v2 0/5] Support for hardware-wrapped inline encryption keys Eric Biggers
2021-09-16 17:49 ` [RFC PATCH v2 1/5] block: add basic hardware-wrapped key support Eric Biggers
2021-09-16 17:49 ` [RFC PATCH v2 2/5] block: add ioctls to create and prepare hardware-wrapped keys Eric Biggers
2021-09-16 17:49 ` [RFC PATCH v2 3/5] fscrypt: improve documentation for inline encryption Eric Biggers
2021-09-21 3:13 ` Eric Biggers [this message]
2021-09-16 17:49 ` [RFC PATCH v2 4/5] fscrypt: allow 256-bit master keys with AES-256-XTS Eric Biggers
2021-09-17 17:46 ` Paul Crowley
2021-09-21 3:16 ` Eric Biggers
2021-09-16 17:49 ` [RFC PATCH v2 5/5] fscrypt: add support for hardware-wrapped keys Eric Biggers
2021-09-27 18:12 ` [RFC PATCH v2 0/5] Support for hardware-wrapped inline encryption keys Eric Biggers
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=YUlN7TY7z5/2EcFF@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=gaurkash@codeaurora.org \
--cc=kernel-team@android.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=satyaprateek2357@gmail.com \
--cc=thara.gopinath@linaro.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).