From: Eric Biggers <ebiggers@kernel.org>
To: fstests@vger.kernel.org
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-fscrypt@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 0/5] xfstests: test f2fs compression+encryption
Date: Wed, 30 Sep 2020 17:25:02 -0700 [thread overview]
Message-ID: <20201001002508.328866-1-ebiggers@kernel.org> (raw)
Add a test which verifies that encryption is done correctly when a file
on f2fs uses both compression and encryption at the same time.
Patches 1-4 add prerequisites for the test, while patch 5 adds the
actual test. Patch 2 also fixes a bug which could cause the existing
test generic/602 to fail in extremely rare cases. See the commit
messages for details.
The new test passes both with and without the inlinecrypt mount option.
It requires CONFIG_F2FS_FS_COMPRESSION=y.
I'd appreciate the f2fs developers taking a look.
Note, there is a quirk where the IVs in compressed files are off by one
from the "natural" values. It's still secure, though it made the test
slightly harder to write. I'm not sure how intentional this quirk was.
Eric Biggers (5):
fscrypt-crypt-util: clean up parsing --block-size and --inode-number
fscrypt-crypt-util: fix IV incrementing for --iv-ino-lblk-32
fscrypt-crypt-util: add --block-number option
common/f2fs: add _require_scratch_f2fs_compression()
f2fs: verify ciphertext of compressed+encrypted file
common/config | 1 +
common/f2fs | 27 +++++
src/fscrypt-crypt-util.c | 98 ++++++++++++------
tests/f2fs/002 | 217 +++++++++++++++++++++++++++++++++++++++
tests/f2fs/002.out | 21 ++++
tests/f2fs/group | 1 +
6 files changed, 334 insertions(+), 31 deletions(-)
create mode 100644 common/f2fs
create mode 100755 tests/f2fs/002
create mode 100644 tests/f2fs/002.out
--
2.28.0
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2020-10-01 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 0:25 Eric Biggers [this message]
2020-10-01 0:25 ` [f2fs-dev] [PATCH 1/5] fscrypt-crypt-util: clean up parsing --block-size and --inode-number Eric Biggers
2020-10-01 0:25 ` [f2fs-dev] [PATCH 2/5] fscrypt-crypt-util: fix IV incrementing for --iv-ino-lblk-32 Eric Biggers
2020-10-01 0:25 ` [f2fs-dev] [PATCH 3/5] fscrypt-crypt-util: add --block-number option Eric Biggers
2020-10-01 0:25 ` [f2fs-dev] [PATCH 4/5] common/f2fs: add _require_scratch_f2fs_compression() Eric Biggers
2020-10-01 0:25 ` [f2fs-dev] [PATCH 5/5] f2fs: verify ciphertext of compressed+encrypted file Eric Biggers
2020-10-07 3:48 ` [f2fs-dev] [PATCH 0/5] xfstests: test f2fs compression+encryption Eric Biggers
2020-10-07 4:27 ` Daeho Jeong
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=20201001002508.328866-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.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 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).