From: Eric Biggers <ebiggers@kernel.org>
To: Jan Prusakowski <jprusakowski@google.com>
Cc: Zorro Lang <zlang@kernel.org>, Chao Yu <chao@kernel.org>,
fstests@vger.kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v2 0/1] Do not run _verify_ciphertext_for_encryption_policy on compressed FS
Date: Mon, 15 Sep 2025 09:34:30 -0500 [thread overview]
Message-ID: <20250915143430.GA1993@quark> (raw)
In-Reply-To: <20250915100451.810719-1-jprusakowski@google.com>
On Mon, Sep 15, 2025 at 12:04:50PM +0200, Jan Prusakowski wrote:
> Changes in v2: (Thanks to Eric for the review)
> - Instead of disabling the test entirely when file compression is used
> we now ensure that compression of the test file is disabled.
>
> Jan Prusakowski (1):
> common/encrypt: Do not run _verify_ciphertext_for_encryption_policy on
> compressed FS
>
> common/encrypt | 7 +++++++
> 1 file changed, 7 insertions(+)
FYI: for a single patch, there's no need for a cover letter. If a
changelog is needed, it should be in the patch itself, just below the
"---" line.
- 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 v2 0/1] Do not run _verify_ciphertext_for_encryption_policy on compressed FS
Date: Mon, 15 Sep 2025 09:34:30 -0500 [thread overview]
Message-ID: <20250915143430.GA1993@quark> (raw)
In-Reply-To: <20250915100451.810719-1-jprusakowski@google.com>
On Mon, Sep 15, 2025 at 12:04:50PM +0200, Jan Prusakowski wrote:
> Changes in v2: (Thanks to Eric for the review)
> - Instead of disabling the test entirely when file compression is used
> we now ensure that compression of the test file is disabled.
>
> Jan Prusakowski (1):
> common/encrypt: Do not run _verify_ciphertext_for_encryption_policy on
> compressed FS
>
> common/encrypt | 7 +++++++
> 1 file changed, 7 insertions(+)
FYI: for a single patch, there's no need for a cover letter. If a
changelog is needed, it should be in the patch itself, just below the
"---" line.
- 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-09-15 14:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 10:04 [PATCH v2 0/1] Do not run _verify_ciphertext_for_encryption_policy on compressed FS Jan Prusakowski
2025-09-15 10:04 ` [f2fs-dev] " Jan Prusakowski via Linux-f2fs-devel
2025-09-15 10:04 ` [PATCH v2 1/1] common/encrypt: " Jan Prusakowski
2025-09-15 10:04 ` [f2fs-dev] " Jan Prusakowski via Linux-f2fs-devel
2025-09-15 14:39 ` Eric Biggers
2025-09-15 14:39 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2025-09-16 12:13 ` Jan Prusakowski
2025-09-16 12:13 ` [f2fs-dev] " Jan Prusakowski via Linux-f2fs-devel
2025-10-03 16:42 ` Eric Biggers
2025-10-03 16:42 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2025-09-15 14:34 ` Eric Biggers [this message]
2025-09-15 14:34 ` [f2fs-dev] [PATCH v2 0/1] " Eric Biggers 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=20250915143430.GA1993@quark \
--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.