[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200520225515.GC19246@sol.localdomain>
Date: Wed, 20 May 2020 15:55:15 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: linux-fscrypt@...r.kernel.org
Cc: linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
Jaegeuk Kim <jaegeuk@...nel.org>,
"Theodore Y . Ts'o" <tytso@....edu>,
Daniel Rosenberg <drosen@...gle.com>
Subject: Re: [PATCH 0/4] fscrypt: make '-o test_dummy_encryption' support v2
policies
On Tue, May 12, 2020 at 04:32:47PM -0700, Eric Biggers wrote:
> v1 encryption policies are deprecated in favor of v2, and some new
> features (e.g. encryption+casefolding) are only being added for v2.
>
> As a result, the "test_dummy_encryption" mount option (which is used for
> encryption I/O testing with xfstests) needs to support v2 policies.
>
> Therefore, this patchset adds support for specifying
> "test_dummy_encryption=v2" (or "test_dummy_encryption=v1").
> To make this possible, it reworks the way the test_dummy_encryption
> mount option is handled to make it more flexible than a flag, and to
> automatically add the test dummy key to the filesystem's keyring.
>
> Patch 4 additionally changes the default to "v2".
>
> This patchset applies to v5.7-rc4.
>
> Eric Biggers (4):
> linux/parser.h: add include guards
> fscrypt: add fscrypt_add_test_dummy_key()
> fscrypt: support test_dummy_encryption=v2
> fscrypt: make test_dummy_encryption use v2 by default
>
All applied to fscrypt.git#master for 5.8
(including the sysfs additions to patch 3, as was discussed)
- Eric
Powered by blists - more mailing lists