From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [PATCH] f2fs_io: support AES_256_HCTR2
Date: Mon, 6 Feb 2023 18:47:25 -0800 [thread overview]
Message-ID: <20230207024725.260092-1-jaegeuk@kernel.org> (raw)
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
tools/f2fs_io/f2fs_io.c | 21 +++++++++++----------
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/tools/f2fs_io/f2fs_io.c b/tools/f2fs_io/f2fs_io.c
index 6dcd84091583..5bc0baf40421 100644
--- a/tools/f2fs_io/f2fs_io.c
+++ b/tools/f2fs_io/f2fs_io.c
@@ -1195,16 +1195,17 @@ static void do_get_filename_encrypt_mode (int argc, char **argv,
const struct cmd_desc *cmd)
{
static const char *enc_name[] = {
- "invalid", /* FS_ENCRYPTION_MODE_INVALID (0) */
- "aes-256-xts", /* FS_ENCRYPTION_MODE_AES_256_XTS (1) */
- "aes-256-gcm", /* FS_ENCRYPTION_MODE_AES_256_GCM (2) */
- "aes-256-cbc", /* FS_ENCRYPTION_MODE_AES_256_CBC (3) */
- "aes-256-cts", /* FS_ENCRYPTION_MODE_AES_256_CTS (4) */
- "aes-128-cbc", /* FS_ENCRYPTION_MODE_AES_128_CBC (5) */
- "aes-128-cts", /* FS_ENCRYPTION_MODE_AES_128_CTS (6) */
- "speck128-256-xts", /* FS_ENCRYPTION_MODE_SPECK128_256_XTS (7) */
- "speck128-256-cts", /* FS_ENCRYPTION_MODE_SPECK128_256_CTS (8) */
- "adiantum", /* FS_ENCRYPTION_MODE_ADIANTUM (9) */
+ "invalid", /* FSCRYPT_MODE_INVALID (0) */
+ "aes-256-xts", /* FSCRYPT_MODE_AES_256_XTS (1) */
+ "aes-256-gcm", /* FSCRYPT_MODE_AES_256_GCM (2) */
+ "aes-256-cbc", /* FSCRYPT_MODE_AES_256_CBC (3) */
+ "aes-256-cts", /* FSCRYPT_MODE_AES_256_CTS (4) */
+ "aes-128-cbc", /* FSCRYPT_MODE_AES_128_CBC (5) */
+ "aes-128-cts", /* FSCRYPT_MODE_AES_128_CTS (6) */
+ "speck128-256-xts", /* FSCRYPT_MODE_SPECK128_256_XTS (7) */
+ "speck128-256-cts", /* FSCRYPT_MODE_SPECK128_256_CTS (8) */
+ "adiantum", /* FSCRYPT_MODE_ADIANTUM (9) */
+ "aes-256-hctr2", /* FSCRYPT_MODE_AES_256_HCTR2 (10) */
};
int fd, mode, ret;
struct fscrypt_get_policy_ex_arg arg;
--
2.39.1.519.gcb327c4b5f-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2023-02-07 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 2:47 Jaegeuk Kim [this message]
2023-02-07 13:31 ` [f2fs-dev] [PATCH] f2fs_io: support AES_256_HCTR2 Chao Yu
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=20230207024725.260092-1-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).