From: Luis Henriques <lhenriques@suse.de>
To: Jeff Layton <jlayton@kernel.org>
Cc: ceph-devel@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH v4 17/17] ceph: add fscrypt ioctls
Date: Thu, 28 Jan 2021 12:22:02 +0000 [thread overview]
Message-ID: <87y2gdi74l.fsf@suse.de> (raw)
In-Reply-To: <20210120182847.644850-18-jlayton@kernel.org> (Jeff Layton's message of "Wed, 20 Jan 2021 13:28:47 -0500")
Jeff Layton <jlayton@kernel.org> writes:
> Most of the ioctls, we gate on the MDS feature support. The exception is
> the key removal and status functions that we still want to work if the
> MDS's were to (inexplicably) lose the feature.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> fs/ceph/ioctl.c | 61 +++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 61 insertions(+)
>
> diff --git a/fs/ceph/ioctl.c b/fs/ceph/ioctl.c
> index 6e061bf62ad4..832909f3eb1b 100644
> --- a/fs/ceph/ioctl.c
> +++ b/fs/ceph/ioctl.c
> @@ -6,6 +6,7 @@
> #include "mds_client.h"
> #include "ioctl.h"
> #include <linux/ceph/striper.h>
> +#include <linux/fscrypt.h>
>
> /*
> * ioctls
> @@ -268,8 +269,29 @@ static long ceph_ioctl_syncio(struct file *file)
> return 0;
> }
>
> +static int vet_mds_for_fscrypt(struct file *file)
> +{
> + int i, ret = -EOPNOTSUPP;
> + struct ceph_mds_client *mdsc = ceph_sb_to_mdsc(file_inode(file)->i_sb);
> +
> + mutex_lock(&mdsc->mutex);
> + for (i = 0; i < mdsc->max_sessions; i++) {
> + struct ceph_mds_session *s = __ceph_lookup_mds_session(mdsc, i);
> +
> + if (!s)
> + continue;
> + if (test_bit(CEPHFS_FEATURE_ALTERNATE_NAME, &s->s_features))
> + ret = 0;
And another one, I believe...? We need this here:
ceph_put_mds_session(s);
Also, isn't this logic broken? Shouldn't we walk through all the sessions
and return 0 only if they all have that feature bit set?
Cheers,
--
Luis
> + break;
> + }
> + mutex_unlock(&mdsc->mutex);
> + return ret;
> +}
> +
> long ceph_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
> {
> + int ret;
> +
> dout("ioctl file %p cmd %u arg %lu\n", file, cmd, arg);
> switch (cmd) {
> case CEPH_IOC_GET_LAYOUT:
> @@ -289,6 +311,45 @@ long ceph_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
>
> case CEPH_IOC_SYNCIO:
> return ceph_ioctl_syncio(file);
> +
> + case FS_IOC_SET_ENCRYPTION_POLICY:
> + ret = vet_mds_for_fscrypt(file);
> + if (ret)
> + return ret;
> + return fscrypt_ioctl_set_policy(file, (const void __user *)arg);
> +
> + case FS_IOC_GET_ENCRYPTION_POLICY:
> + ret = vet_mds_for_fscrypt(file);
> + if (ret)
> + return ret;
> + return fscrypt_ioctl_get_policy(file, (void __user *)arg);
> +
> + case FS_IOC_GET_ENCRYPTION_POLICY_EX:
> + ret = vet_mds_for_fscrypt(file);
> + if (ret)
> + return ret;
> + return fscrypt_ioctl_get_policy_ex(file, (void __user *)arg);
> +
> + case FS_IOC_ADD_ENCRYPTION_KEY:
> + ret = vet_mds_for_fscrypt(file);
> + if (ret)
> + return ret;
> + return fscrypt_ioctl_add_key(file, (void __user *)arg);
> +
> + case FS_IOC_REMOVE_ENCRYPTION_KEY:
> + return fscrypt_ioctl_remove_key(file, (void __user *)arg);
> +
> + case FS_IOC_REMOVE_ENCRYPTION_KEY_ALL_USERS:
> + return fscrypt_ioctl_remove_key_all_users(file, (void __user *)arg);
> +
> + case FS_IOC_GET_ENCRYPTION_KEY_STATUS:
> + return fscrypt_ioctl_get_key_status(file, (void __user *)arg);
> +
> + case FS_IOC_GET_ENCRYPTION_NONCE:
> + ret = vet_mds_for_fscrypt(file);
> + if (ret)
> + return ret;
> + return fscrypt_ioctl_get_nonce(file, (void __user *)arg);
> }
>
> return -ENOTTY;
> --
>
> 2.29.2
>
next prev parent reply other threads:[~2021-01-28 12:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 18:28 [RFC PATCH v4 00/17] ceph+fscrypt: context, filename and symlink support Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 01/17] vfs: export new_inode_pseudo Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 02/17] fscrypt: export fscrypt_base64_encode and fscrypt_base64_decode Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 03/17] fscrypt: export fscrypt_fname_encrypt and fscrypt_fname_encrypted_size Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 04/17] fscrypt: add fscrypt_context_for_new_inode Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 05/17] ceph: crypto context handling for ceph Jeff Layton
2021-01-22 16:41 ` Luis Henriques
2021-01-22 17:26 ` Jeff Layton
2021-01-25 10:14 ` Luis Henriques
2021-01-20 18:28 ` [RFC PATCH v4 06/17] ceph: implement -o test_dummy_encryption mount option Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 07/17] ceph: preallocate inode for ops that may create one Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 08/17] ceph: add routine to create fscrypt context prior to RPC Jeff Layton
2021-01-22 16:50 ` Luis Henriques
2021-01-22 17:32 ` Jeff Layton
2021-01-25 10:14 ` Luis Henriques
2021-01-20 18:28 ` [RFC PATCH v4 09/17] ceph: make ceph_msdc_build_path use ref-walk Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 10/17] ceph: add encrypted fname handling to ceph_mdsc_build_path Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 11/17] ceph: decode alternate_name in lease info Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 12/17] ceph: send altname in MClientRequest Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 13/17] ceph: add support to readdir for encrypted filenames Jeff Layton
2021-01-28 11:33 ` Luis Henriques
2021-01-28 13:41 ` Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 14/17] ceph: add fscrypt support to ceph_fill_trace Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 15/17] ceph: make d_revalidate call fscrypt revalidator for encrypted dentries Jeff Layton
2021-02-01 17:18 ` Luis Henriques
2021-02-01 18:41 ` Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 16/17] ceph: create symlinks with encrypted and base64-encoded targets Jeff Layton
2021-01-25 16:03 ` Luis Henriques
2021-01-25 18:31 ` Jeff Layton
2021-01-20 18:28 ` [RFC PATCH v4 17/17] ceph: add fscrypt ioctls Jeff Layton
2021-01-28 12:22 ` Luis Henriques [this message]
2021-01-28 13:44 ` Jeff Layton
2021-01-28 14:09 ` Luis Henriques
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=87y2gdi74l.fsf@suse.de \
--to=lhenriques@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).