From: tytso@mit.edu
To: Satya Tangirala <satyat@google.com>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-ext4@vger.kernel.org, Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH v4 1/4] fs: introduce SB_INLINECRYPT
Date: Wed, 8 Jul 2020 13:07:14 -0400 [thread overview]
Message-ID: <20200708170714.GD1627842@mit.edu> (raw)
In-Reply-To: <20200702015607.1215430-2-satyat@google.com>
On Thu, Jul 02, 2020 at 01:56:04AM +0000, Satya Tangirala wrote:
> Introduce SB_INLINECRYPT, which is set by filesystems that wish to use
> blk-crypto for file content en/decryption. This flag maps to the
> '-o inlinecrypt' mount option which multiple filesystems will implement,
> and code in fs/crypto/ needs to be able to check for this mount option
> in a filesystem-independent way.
>
> Signed-off-by: Satya Tangirala <satyat@google.com>
> Reviewed-by: Eric Biggers <ebiggers@google.com>
Reviewed-by: Theodore Ts'o <tytso@mit.edu>
next prev parent reply other threads:[~2020-07-08 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 1:56 [PATCH v4 0/4] Inline Encryption Support for fscrypt Satya Tangirala
2020-07-02 1:56 ` [PATCH v4 1/4] fs: introduce SB_INLINECRYPT Satya Tangirala
2020-07-08 17:07 ` tytso [this message]
2020-07-02 1:56 ` [PATCH v4 2/4] fscrypt: add inline encryption support Satya Tangirala
2020-07-08 17:14 ` tytso
2020-07-02 1:56 ` [PATCH v4 3/4] f2fs: " Satya Tangirala
2020-07-02 1:56 ` [PATCH v4 4/4] ext4: " Satya Tangirala
2020-07-08 17:18 ` tytso
2020-07-08 17:34 ` Eric Biggers
2020-07-07 18:08 ` [PATCH v4 0/4] Inline Encryption Support for fscrypt 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=20200708170714.GD1627842@mit.edu \
--to=tytso@mit.edu \
--cc=ebiggers@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=satyat@google.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).