From: Eric Biggers <ebiggers@kernel.org>
To: Weichao Guo <guoweichao@oppo.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs-tools: support print_xattr_entry with fscrypt context v2
Date: Thu, 13 Jul 2023 00:22:28 -0700 [thread overview]
Message-ID: <20230713072228.GD2199@sol.localdomain> (raw)
In-Reply-To: <20230712102331.4079126-1-guoweichao@oppo.com>
Hi Weichao,
On Wed, Jul 12, 2023 at 06:23:31PM +0800, Weichao Guo via Linux-f2fs-devel wrote:
> Signed-off-by: Weichao Guo <guoweichao@oppo.com>
> Signed-off-by: Sheng Yong <shengyong@oppo.com>
> ---
> fsck/mount.c | 44 +++++++++++++++++++++++++++---------------
> fsck/xattr.h | 54 +++++++++++++++++++++++++++++++++++++++++++---------
> 2 files changed, 74 insertions(+), 24 deletions(-)
>
> diff --git a/fsck/mount.c b/fsck/mount.c
> index 397feb5..b9696c4 100644
> --- a/fsck/mount.c
> +++ b/fsck/mount.c
> @@ -196,7 +196,7 @@ static void print_xattr_entry(const struct f2fs_xattr_entry *ent)
> {
> const u8 *value = (const u8 *)&ent->e_name[ent->e_name_len];
> const int size = le16_to_cpu(ent->e_value_size);
> - const struct fscrypt_context *ctx;
> + const union fscrypt_context *ctx;
> int i;
>
> MSG(0, "\nxattr: e_name_index:%d e_name:", ent->e_name_index);
> @@ -213,21 +213,35 @@ static void print_xattr_entry(const struct f2fs_xattr_entry *ent)
> return;
> #endif
> case F2FS_XATTR_INDEX_ENCRYPTION:
> - ctx = (const struct fscrypt_context *)value;
> - if (size != sizeof(*ctx) ||
> - ctx->format != FS_ENCRYPTION_CONTEXT_FORMAT_V1)
> + ctx = (const union fscrypt_context *)value;
> + if (size != fscrypt_context_size(ctx))
> break;
> - MSG(0, "format: %d\n", ctx->format);
> - MSG(0, "contents_encryption_mode: 0x%x\n", ctx->contents_encryption_mode);
> - MSG(0, "filenames_encryption_mode: 0x%x\n", ctx->filenames_encryption_mode);
> - MSG(0, "flags: 0x%x\n", ctx->flags);
> - MSG(0, "master_key_descriptor: ");
> - for (i = 0; i < FS_KEY_DESCRIPTOR_SIZE; i++)
> - MSG(0, "%02X", ctx->master_key_descriptor[i]);
> - MSG(0, "\nnonce: ");
> - for (i = 0; i < FS_KEY_DERIVATION_NONCE_SIZE; i++)
> - MSG(0, "%02X", ctx->nonce[i]);
> - MSG(0, "\n");
> + switch (ctx->version) {
> + case FSCRYPT_CONTEXT_V1:
> + MSG(0, "format: %d\n", ctx->version);
> + MSG(0, "contents_encryption_mode: 0x%x\n", ctx->v1.contents_encryption_mode);
> + MSG(0, "filenames_encryption_mode: 0x%x\n", ctx->v1.filenames_encryption_mode);
> + MSG(0, "flags: 0x%x\n", ctx->v1.flags);
> + MSG(0, "master_key_descriptor: ");
> + for (i = 0; i < FSCRYPT_KEY_DESCRIPTOR_SIZE; i++)
> + MSG(0, "%02X", ctx->v1.master_key_descriptor[i]);
> + MSG(0, "\nnonce: ");
> + for (i = 0; i < FSCRYPT_FILE_NONCE_SIZE; i++)
> + MSG(0, "%02X", ctx->v1.nonce[i]);
> + MSG(0, "\n");
> + case FSCRYPT_CONTEXT_V2:
> + MSG(0, "format: %d\n", ctx->version);
> + MSG(0, "contents_encryption_mode: 0x%x\n", ctx->v2.contents_encryption_mode);
> + MSG(0, "filenames_encryption_mode: 0x%x\n", ctx->v2.filenames_encryption_mode);
> + MSG(0, "flags: 0x%x\n", ctx->v2.flags);
> + MSG(0, "master_key_identifier: ");
> + for (i = 0; i < FSCRYPT_KEY_IDENTIFIER_SIZE; i++)
> + MSG(0, "%02X", ctx->v2.master_key_identifier[i]);
> + MSG(0, "\nnonce: ");
> + for (i = 0; i < FSCRYPT_FILE_NONCE_SIZE; i++)
> + MSG(0, "%02X", ctx->v2.nonce[i]);
> + MSG(0, "\n");
> + }
> return;
The FSCRYPT_CONTEXT_V1 case is falling through to FSCRYPT_CONTEXT_V2. Also,
this patch makes the values of encryption xattrs with unknown versions no longer
be shown. To fix this, there needs to be a return at end of each case (v1 and
v2), and the return after the switch statement needs to be a break.
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2023-07-13 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 10:23 [f2fs-dev] [PATCH] f2fs-tools: support print_xattr_entry with fscrypt context v2 Weichao Guo via Linux-f2fs-devel
2023-07-13 7:22 ` Eric Biggers [this message]
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=20230713072228.GD2199@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=guoweichao@oppo.com \
--cc=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).