From: Jeff Layton <jlayton@kernel.org>
To: "Luís Henriques" <lhenriques@suse.de>,
"Xiubo Li" <xiubli@redhat.com>,
"Ilya Dryomov" <idryomov@gmail.com>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ceph: support legacy v1 encryption policy keysetup
Date: Fri, 25 Mar 2022 13:06:35 -0400 [thread overview]
Message-ID: <e81281e69aa29cc10241bbff60283ca7baed87ea.camel@kernel.org> (raw)
In-Reply-To: <20220325164947.22062-1-lhenriques@suse.de>
On Fri, 2022-03-25 at 16:49 +0000, Luís Henriques wrote:
> fstests make use of legacy keysetup where the key description uses a
> filesystem-specific prefix. Add this ceph-specific prefix to the
> fscrypt_operations data structure.
>
> Signed-off-by: Luís Henriques <lhenriques@suse.de>
> ---
> fs/ceph/crypto.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/ceph/crypto.c b/fs/ceph/crypto.c
> index c2e28ae54323..2a8f95885e7d 100644
> --- a/fs/ceph/crypto.c
> +++ b/fs/ceph/crypto.c
> @@ -77,6 +77,7 @@ static const union fscrypt_policy *ceph_get_dummy_policy(struct super_block *sb)
> }
>
> static struct fscrypt_operations ceph_fscrypt_ops = {
> + .key_prefix = "ceph:",
> .get_context = ceph_crypt_get_context,
> .set_context = ceph_crypt_set_context,
> .get_dummy_policy = ceph_get_dummy_policy,
Good catch, thanks! Merged into wip-fscrypt.
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2022-03-25 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 16:49 [PATCH] ceph: support legacy v1 encryption policy keysetup Luís Henriques
2022-03-25 17:06 ` Jeff Layton [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=e81281e69aa29cc10241bbff60283ca7baed87ea.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=lhenriques@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xiubli@redhat.com \
/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