From: Eric Biggers <ebiggers@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: linux-xfs@vger.kernel.org, linux-fscrypt@vger.kernel.org,
fstests@vger.kernel.org
Subject: Re: [xfsprogs PATCH] xfs_io/encrypt: support specifying crypto data unit size
Date: Thu, 16 Nov 2023 21:24:30 -0800 [thread overview]
Message-ID: <20231117052430.GB972@sol.localdomain> (raw)
In-Reply-To: <h7e7q6g7ti4mbre55ap6x5o6suzdiiyykxtn5pgfsf2w6y7esx@tg2qxsplx2zb>
On Thu, Nov 16, 2023 at 11:04:16AM +0100, Carlos Maiolino wrote:
> On Wed, Nov 15, 2023 at 07:58:46PM -0800, Eric Biggers wrote:
> > On Thu, Oct 12, 2023 at 11:26:39PM -0700, Eric Biggers wrote:
> > > From: Eric Biggers <ebiggers@google.com>
> > >
> > > Add an '-s' option to the 'set_encpolicy' command of xfs_io to allow
> > > exercising the log2_data_unit_size field that is being added to struct
> > > fscrypt_policy_v2 (kernel patch:
> > > https://lore.kernel.org/linux-fscrypt/20230925055451.59499-6-ebiggers@kernel.org).
> > >
> > > The xfs_io support is needed for xfstests
> > > (https://lore.kernel.org/fstests/20231013061403.138425-1-ebiggers@kernel.org),
> > > which currently relies on xfs_io to access the encryption ioctls.
> > >
> > > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > > ---
> > > configure.ac | 1 +
> > > include/builddefs.in | 4 +++
> > > io/encrypt.c | 72 ++++++++++++++++++++++++++++++++-----------
> > > m4/package_libcdev.m4 | 21 +++++++++++++
> > > man/man8/xfs_io.8 | 5 ++-
> > > 5 files changed, 84 insertions(+), 19 deletions(-)
> >
> > Hi! Any feedback on this patch?
>
> I've got a limited bandwidth these days, I'll try to review this sometime
> around next week.
>
Thanks Carlos.
BTW, this is really just for xfstests. To be honest, it might be a good idea to
remove the encryption commands from xfs_io, and make the encryption tests just
use an xfstests helper program, potentially in combination with fscryptctl
(https://github.com/google/fscryptctl) which now contains most of this
functionality too. Then the XFS folks would have less to worry about. Maybe
xfs_io has a backwards compatibility guarantee that makes this impossible, but
if not then it may be worth thinking about if the XFS folks don't want to have
to keep reviewing patches to the encryption commands like this. The xfs_io
commands were what Dave had requested when I added the first encryption tests
back in 2016, so I did it that way, but maybe preferences have changed.
Anyway, review and/or thoughts are appreciated.
- Eric
next prev parent reply other threads:[~2023-11-17 5:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <kryIlLZ9Vvv1wM_-rlFWqxRV8JqiDM2Y2h6TasXqWOrbeWn6yE0GhLlL-21EqfI8UI99uzD3OacG0Fp0uLq2gQ==@protonmail.internalid>
2023-10-13 6:26 ` [xfsprogs PATCH] xfs_io/encrypt: support specifying crypto data unit size Eric Biggers
2023-11-16 3:58 ` Eric Biggers
2023-11-16 10:04 ` Carlos Maiolino
2023-11-17 5:24 ` Eric Biggers [this message]
2023-11-29 14:21 ` Carlos Maiolino
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=20231117052430.GB972@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=cem@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-xfs@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