Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Satya Tangirala <satyat@google.com>,
	Theodore Ts'o <tytso@mit.edu>,
	Andreas Dilger <adilger.kernel@dilger.ca>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH v4 0/4] Inline Encryption Support for fscrypt
Date: Tue, 7 Jul 2020 11:08:54 -0700	[thread overview]
Message-ID: <20200707180854.GB839@sol.localdomain> (raw)
In-Reply-To: <20200702015607.1215430-1-satyat@google.com>

On Thu, Jul 02, 2020 at 01:56:03AM +0000, Satya Tangirala wrote:
> This patch series adds support for Inline Encryption to fscrypt, f2fs
> and ext4. It builds on the inline encryption support now present in
> the block layer, and has been rebased on v5.8-rc3. Note that Patches 1 and
> 2 can be applied independently of Patches 3 and 4 (and Patches 3 and 4 can
> be applied independently of each other).
> 
> This patch series previously went though a number of iterations as part
> of the "Inline Encryption Support" patchset (last version was v13:
> https://lkml.kernel.org/r/20200514003727.69001-1-satyat@google.com).
> 
> Patch 1 introduces the SB_INLINECRYPT sb options, which filesystems
> should set if they want to use blk-crypto for file content en/decryption.
> 
> Patch 2 adds inline encryption support to fscrypt. To use inline
> encryption with fscrypt, the filesystem must set the above mentioned
> SB_INLINECRYPT sb option. When this option is set, the contents of
> encrypted files will be en/decrypted using blk-crypto.
> 
> Patches 3 and 4 wire up f2fs and ext4 respectively to fscrypt support for
> inline encryption, and e.g ensure that bios are submitted with blocks
> that not only are contiguous, but also have continuous DUNs.

I've applied patches 1-3 to fscrypt.git#master for 5.9.
Any additional reviews are still appreciated though.

Ted and Andreas, can I get your Acked-by on patch 4?

- Eric

      parent reply	other threads:[~2020-07-07 18:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02  1:56 Satya Tangirala
2020-07-02  1:56 ` [PATCH v4 1/4] fs: introduce SB_INLINECRYPT Satya Tangirala
2020-07-08 17:07   ` tytso
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 ` Eric Biggers [this message]

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=20200707180854.GB839@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=adilger.kernel@dilger.ca \
    --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 \
    --cc=tytso@mit.edu \
    --subject='Re: [PATCH v4 0/4] Inline Encryption Support for fscrypt' \
    /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

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).