From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fscrypt: show more information of policy
Date: Mon, 30 Mar 2020 13:18:46 -0700 [thread overview]
Message-ID: <20200330201846.GA212732@google.com> (raw)
In-Reply-To: <20200330195143.GB108564@gmail.com>
On 03/30, Eric Biggers wrote:
> On Mon, Mar 30, 2020 at 12:25:24PM -0700, Jaegeuk Kim wrote:
> > From: Jaegeuk Kim <jaegeuk@google.com>
> >
> > This patch gives more information of encryption policy.
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
> > Change-Id: I04a6826aa4497554ce79d884d495b3dda1b64fac
> > ---
> > tools/f2fscrypt.c | 34 ++++++++++++++++++++++++++++++++++
> > 1 file changed, 34 insertions(+)
> >
> > diff --git a/tools/f2fscrypt.c b/tools/f2fscrypt.c
> > index fe3e0ff..bb3e70f 100644
> > --- a/tools/f2fscrypt.c
> > +++ b/tools/f2fscrypt.c
>
> I'm a little confused why the f2fscrypt tool even exists? Who is using it? It
> looks like this code was all copied from e4crypt, which is no longer being
> maintained either as there are now better filesystem-independent tools:
>
> - https://github.com/google/fscrypt
> - https://github.com/google/fscryptctl
> - https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/tree/io/encrypt.c
>
> Would one of those work for you instead?
I'm using it occasionally in Android. I think it'd be great to add it in f2fs_io
likewise xfs_io tho, it'd be also okay to add one of projects in AOSP, if you
have some bandwidth. If you have any plan, I'd okay to remove f2fscrypt in
f2fs-tools.
>
> > @@ -63,6 +63,8 @@
> > #define F2FS_ENCRYPTION_MODE_AES_256_GCM 2
> > #define F2FS_ENCRYPTION_MODE_AES_256_CBC 3
> > #define F2FS_ENCRYPTION_MODE_AES_256_CTS 4
> > +#define F2FS_ENCRYPTION_MODE_ADIANTUM 9
> > +#define F2FS_ENCRYPTION_MODE_PRIVATE 127
>
> This doesn't match the list of encryption modes from the UAPI header.
Will fix.
>
> > +static const char *get_crypt_mode(int mode)
> > +{
> > + int i;
> > +
> > + for (i = 0; i < (sizeof(enc_mode_str) / sizeof(enc_mode_str[0])); ++i) {
> > + if (mode == enc_mode_str[i].mode) {
> > + return enc_mode_str[i].name;
> > + }
> > + }
> > + return "N/A";
> > +}
>
> If the mode number is unrecognized, it should show the number.
Will fix.
Thanks,
_______________________________________________
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:[~2020-03-30 20:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 19:25 [f2fs-dev] [PATCH] f2fscrypt: show more information of policy Jaegeuk Kim
2020-03-30 19:51 ` Eric Biggers
2020-03-30 20:18 ` Jaegeuk Kim [this message]
2020-03-30 20:37 ` Eric Biggers
2020-03-31 4:03 ` Jaegeuk Kim
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=20200330201846.GA212732@google.com \
--to=jaegeuk@kernel.org \
--cc=ebiggers@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).