Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   "Theodore Ts'o" <tytso@mit.edu>
To:     linux-ext4@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>
Cc:     "Theodore Ts'o" <tytso@mit.edu>, linux-fscrypt@vger.kernel.org
Subject: Re: [PATCH v4] ext4: only allow test_dummy_encryption when supported
Date:   Sat, 21 May 2022 22:31:47 -0400
Message-Id: <165318668323.1718738.16352700096125589456.b4-ty@mit.edu>
In-Reply-To: <20220519204437.61645-1-ebiggers@kernel.org>
References: <20220519204437.61645-1-ebiggers@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 19 May 2022 13:44:37 -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> Make the test_dummy_encryption mount option require that the encrypt
> feature flag be already enabled on the filesystem, rather than
> automatically enabling it.  Practically, this means that "-O encrypt"
> will need to be included in MKFS_OPTIONS when running xfstests with the
> test_dummy_encryption mount option.  (ext4/053 also needs an update.)
> 
> [...]

I've replaced the older version of the commit with this one, thanks!

[1/1] ext4: only allow test_dummy_encryption when supported
      commit: d177c151d74881536aa6b58f450c70fd5a7b6c1a

Best regards,
-- 
Theodore Ts'o <tytso@mit.edu>