From: Eric Biggers <ebiggers@kernel.org>
To: Jan Prusakowski <jprusakowski@google.com>
Cc: Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, Chao Yu <chao@kernel.org>,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v3] common/encrypt: Explicitly set the test file to uncompressed
Date: Mon, 6 Oct 2025 08:44:01 -0700 [thread overview]
Message-ID: <20251006154401.GA1637@sol> (raw)
In-Reply-To: <20251006095813.3497619-1-jprusakowski@google.com>
On Mon, Oct 06, 2025 at 11:58:13AM +0200, Jan Prusakowski wrote:
> verify_ciphertext_for_encryption_policy() checks if encryption works
> correctly by reading encrypted file's contents directly from a block device and
> comparing it to a known good ciphertext.
>
> This, however, won't work if the test file is also compressed. So this patch
> adds a check if a test file is compressed and disables its compression in this
> case.
>
> Signed-off-by: Jan Prusakowski <jprusakowski@google.com>
Reviewed-by: Eric Biggers <ebiggers@kernel.org>
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jan Prusakowski <jprusakowski@google.com>
Cc: jaegeuk@kernel.org, Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] common/encrypt: Explicitly set the test file to uncompressed
Date: Mon, 6 Oct 2025 08:44:01 -0700 [thread overview]
Message-ID: <20251006154401.GA1637@sol> (raw)
In-Reply-To: <20251006095813.3497619-1-jprusakowski@google.com>
On Mon, Oct 06, 2025 at 11:58:13AM +0200, Jan Prusakowski wrote:
> verify_ciphertext_for_encryption_policy() checks if encryption works
> correctly by reading encrypted file's contents directly from a block device and
> comparing it to a known good ciphertext.
>
> This, however, won't work if the test file is also compressed. So this patch
> adds a check if a test file is compressed and disables its compression in this
> case.
>
> Signed-off-by: Jan Prusakowski <jprusakowski@google.com>
Reviewed-by: Eric Biggers <ebiggers@kernel.org>
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2025-10-06 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 9:58 [PATCH v3] common/encrypt: Explicitly set the test file to uncompressed Jan Prusakowski
2025-10-06 9:58 ` [f2fs-dev] " Jan Prusakowski via Linux-f2fs-devel
2025-10-06 15:44 ` Eric Biggers [this message]
2025-10-06 15:44 ` Eric Biggers via Linux-f2fs-devel
2025-10-11 7:13 ` Chao Yu
2025-10-11 7:13 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
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=20251006154401.GA1637@sol \
--to=ebiggers@kernel.org \
--cc=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jprusakowski@google.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zlang@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.