ceph+fscrypt: context, filename and symlink support
Subsystems (3)
v6 cover ceph+fscrypt: context, filename and symlink support
The main change in this posting is in the detection of fscrypted inodes. The older set would grovel around in the xattr blob to see if it had an "encryption.ctx" xattr. This was problematic if the MDS didn't send xattrs in the trace, and not very efficient.
This posting changes it to use the new "fscrypt" flag, which should always be reported by the MDS (Luis, I'm hoping this may fix the issues you were seeing with dcache coherency).
This unfortunately requires an MDS fix, but that should hopefully make it in and be backported to Pacific fairly soon:
https://github.com/ceph/ceph/pull/40828
We also now handle get_name in the NFS export code correctly.
Aside from that, there are better changelogs, particularly on the fscrypt and vfs patches, and some smaller bugfixes and optimizations.
Jeff Layton (20):
vfs: export new_inode_pseudo
fscrypt: export fscrypt_base64_encode and fscrypt_base64_decode
fscrypt: export fscrypt_fname_encrypt and fscrypt_fname_encrypted_size
fscrypt: add fscrypt_context_for_new_inode
ceph: crypto context handling for ceph
ceph: implement -o test_dummy_encryption mount option
ceph: preallocate inode for ops that may create one
ceph: add routine to create fscrypt context prior to RPC
ceph: make ceph_msdc_build_path use ref-walk
ceph: add encrypted fname handling to ceph_mdsc_build_path
ceph: decode alternate_name in lease info
ceph: send altname in MClientRequest
ceph: properly set DCACHE_NOKEY_NAME flag in lookup
ceph: make d_revalidate call fscrypt revalidator for encrypted
dentries
ceph: add helpers for converting names for userland presentation
ceph: add fscrypt support to ceph_fill_trace
ceph: add support to readdir for encrypted filenames
ceph: create symlinks with encrypted and base64-encoded targets
ceph: make ceph_get_name decrypt filenames
ceph: add fscrypt ioctls
fs/ceph/Makefile | 1 + fs/ceph/crypto.c | 185 ++++++++++++++++++++++ fs/ceph/crypto.h | 101 ++++++++++++ fs/ceph/dir.c | 178 ++++++++++++++++----- fs/ceph/export.c | 42 +++-- fs/ceph/file.c | 58 ++++--- fs/ceph/inode.c | 248 ++++++++++++++++++++++++++--- fs/ceph/ioctl.c | 93 +++++++++++ fs/ceph/mds_client.c | 303 ++++++++++++++++++++++++++++++------ fs/ceph/mds_client.h | 15 +- fs/ceph/super.c | 80 +++++++++- fs/ceph/super.h | 15 +- fs/ceph/xattr.c | 5 + fs/crypto/fname.c | 53 +++++-- fs/crypto/fscrypt_private.h | 9 +- fs/crypto/hooks.c | 6 +- fs/crypto/policy.c | 34 +++- fs/inode.c | 1 + include/linux/fscrypt.h | 10 ++ 19 files changed, 1263 insertions(+), 174 deletions(-) create mode 100644 fs/ceph/crypto.c create mode 100644 fs/ceph/crypto.h
Signature · 1 line
2.30.2
RFC PATCH v6 1/20 vfs: export new_inode_pseudo
Ceph needs to be able to allocate inodes ahead of a create that might involve a fscrypt-encrypted inode. new_inode() almost fits the bill, but it puts the inode on the sb->s_inodes list and when we go to hash it, that might be done again.
We could work around that by setting I_CREATING on the new inode, but that causes ilookup5 to return -ESTALE if something tries to find it before I_NEW is cleared. This is desirable behavior for most filesystems, but doesn't work for ceph.
To work around all of this, just use new_inode_pseudo which doesn't add it to the sb->s_inodes list.
--- fs/inode.c | 1 + 1 file changed, 1 insertion(+)
fs/inode.c +1 -0
@@ -935,6 +935,7 @@ struct inode *new_inode_pseudo(struct super_block *sb) }return inode; } +EXPORT_SYMBOL (new_inode_pseudo);/** * new_inode - obtain an inode
Signature · 1 line
2.30.2
RFC PATCH v6 2/20 fscrypt: export fscrypt_base64_encode and fscrypt_base64_decode
In reply to Jeff LaytonCeph is going to add fscrypt support, but we still want encrypted filenames to be composed of printable characters, so we can maintain compatibility with clients that don't support fscrypt.
We could just adopt fscrypt's current nokey name format, but that is subject to change in the future, and it also contains dirhash fields that we don't need for cephfs. Because of this, we're going to concoct our own scheme for encoding encrypted filenames. It's very similar to fscrypt's current scheme, but doesn't bother with the dirhash fields.
The ceph encoding scheme will use base64 encoding as well, and we also want it to avoid characters that are illegal in filenames. Export the fscrypt base64 encoding/decoding routines so we can use them in ceph's fscrypt implementation.
--- fs/crypto/fname.c | 34 ++++++++++++++++++++++++---------- include/linux/fscrypt.h | 5 +++++ 2 files changed, 29 insertions(+), 10 deletions(-)
fs/crypto/fname.c +24 -10
@@ -178,10 +178,8 @@ static int fname_decrypt(const struct inode *inode,static const char lookup_table[65 ] ="ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+," ; -#define BASE64_CHARS (nbytes) DIV_ROUND_UP((nbytes) * 4, 3) -/** -* base64_encode() - base64-encode some bytes +* fscrypt_base64_encode() - base64-encode some bytes * @src: the bytes to encode * @len: number of bytes to encode * @dst: (output) the base64-encoded string. Not NUL-terminated.
@@ -191,7 +189,7 @@ static const char lookup_table[65] =* * Return: length of the encoded string */ -static int base64_encode (const u8 *src,int len,char *dst) +int fscrypt_base64_encode (const u8 *src,int len,char *dst) {int i, bits =0 , ac =0 ;char *cp = dst;
@@ -209,8 +207,20 @@ static int base64_encode(const u8 *src, int len, char *dst) *cp++ = lookup_table[ac &0x3f ];return cp - dst; } +EXPORT_SYMBOL (fscrypt_base64_encode); -static int base64_decode (const char *src,int len,u8 *dst) +/** +* fscrypt_base64_decode() - base64-decode some bytes +* @src: the bytes to decode +* @len: number of bytes to decode +* @dst: (output) decoded binary data +* +* Decode an input string that was previously encoded using +* fscrypt_base64_encode. +* +* Return: length of the decoded binary data +*/ +int fscrypt_base64_decode (const char *src,int len,u8 *dst) {int i, bits =0 , ac =0 ;const char *p;
@@ -232,6 +242,7 @@ static int base64_decode(const char *src, int len, u8 *dst)return -1 ;return cp - dst; } +EXPORT_SYMBOL (fscrypt_base64_decode); bool fscrypt_fname_encrypted_size(const union fscrypt_policy *policy, u32 orig_len, u32 max_len,
@@ -263,8 +274,9 @@ bool fscrypt_fname_encrypted_size(const union fscrypt_policy *policy,int fscrypt_fname_alloc_buffer (u32 max_encrypted_len,struct fscrypt_str *crypto_str) { -const u32 max_encoded_len =BASE64_CHARS (FSCRYPT_NOKEY_NAME_MAX );u32 max_presented_len; +const u32 max_encoded_len = +FSCRYPT_BASE64_CHARS (FSCRYPT_NOKEY_NAME_MAX ); max_presented_len =max (max_encoded_len, max_encrypted_len);
@@ -342,7 +354,7 @@ int fscrypt_fname_disk_to_usr(const struct inode *inode, offsetof(struct fscrypt_nokey_name, bytes)); BUILD_BUG_ON(offsetofend(struct fscrypt_nokey_name, bytes) != offsetof(struct fscrypt_nokey_name, sha256)); -BUILD_BUG_ON (BASE64_CHARS (FSCRYPT_NOKEY_NAME_MAX ) >NAME_MAX ); +BUILD_BUG_ON (FSCRYPT_BASE64_CHARS (FSCRYPT_NOKEY_NAME_MAX ) >NAME_MAX );if (hash) { nokey_name.dirhash[0 ] = hash;
@@ -362,7 +374,8 @@ int fscrypt_fname_disk_to_usr(const struct inode *inode, nokey_name.sha256); size =FSCRYPT_NOKEY_NAME_MAX ; } - oname->len =base64_encode ((const u8 *)&nokey_name, size, oname->name); + oname->len =fscrypt_base64_encode ((const u8 *)&nokey_name, size, + oname->name);return 0 ; }EXPORT_SYMBOL (fscrypt_fname_disk_to_usr);
@@ -436,14 +449,15 @@ int fscrypt_setup_filename(struct inode *dir, const struct qstr *iname,* user-supplied name */ -if (iname->len >BASE64_CHARS (FSCRYPT_NOKEY_NAME_MAX )) +if (iname->len >FSCRYPT_BASE64_CHARS (FSCRYPT_NOKEY_NAME_MAX ))return -ENOENT ; fname->crypto_buf.name =kmalloc (FSCRYPT_NOKEY_NAME_MAX ,GFP_KERNEL );if (fname->crypto_buf.name ==NULL )return -ENOMEM ; - ret =base64_decode (iname->name, iname->len, fname->crypto_buf.name); + ret =fscrypt_base64_decode (iname->name, iname->len, + fname->crypto_buf.name); if (ret < (int)offsetof(struct fscrypt_nokey_name, bytes[1]) || (ret > offsetof(struct fscrypt_nokey_name, sha256) && ret != FSCRYPT_NOKEY_NAME_MAX)) {
include/linux/fscrypt.h +5 -0
@@ -46,6 +46,9 @@ struct fscrypt_name {/* Maximum value for the third parameter of fscrypt_operations.set_context(). */ #define FSCRYPT_SET_CONTEXT_MAX_SIZE 40 +/* Calculate worst-case base64 encoding inflation */ +#define FSCRYPT_BASE64_CHARS (nbytes) DIV_ROUND_UP((nbytes) * 4, 3) +#ifdef CONFIG_FS_ENCRYPTION /* * fscrypt superblock flags
@@ -207,6 +210,8 @@ void fscrypt_free_inode(struct inode *inode);int fscrypt_drop_inode (struct inode *inode);/* fname.c */ +int fscrypt_base64_encode (const u8 *src,int len,char *dst); +int fscrypt_base64_decode (const char *src,int len,u8 *dst);int fscrypt_setup_filename (struct inode *inode,const struct qstr *iname,int lookup,struct fscrypt_name *fname);
Signature · 1 line
2.30.2
RFC PATCH v6 3/20 fscrypt: export fscrypt_fname_encrypt and fscrypt_fname_encrypted_size
In reply to Jeff LaytonFor ceph, we want to use our own scheme for handling filenames that are are longer than NAME_MAX after encryption and base64 encoding. This allows us to have a consistent view of the encrypted filenames for clients that don't support fscrypt and clients that do but that don't have the key.
Currently, fs/crypto only supports encrypting filenames using fscrypt_setup_filename, but that also handles encoding nokey names. Ceph can't use that because it handles nokey names in a different way.
Export fscrypt_fname_encrypt. Rename fscrypt_fname_encrypted_size to __fscrypt_fname_encrypted_size and add a new wrapper called fscrypt_fname_encrypted_size that takes an inode argument rather than a pointer to a fscrypt_policy union.
--- fs/crypto/fname.c | 19 ++++++++++++++----- fs/crypto/fscrypt_private.h | 9 +++------ fs/crypto/hooks.c | 6 +++--- include/linux/fscrypt.h | 4 ++++ 4 files changed, 24 insertions(+), 14 deletions(-)
fs/crypto/fname.c +14 -5
@@ -126,6 +126,7 @@ int fscrypt_fname_encrypt(const struct inode *inode, const struct qstr *iname,return 0 ; } +EXPORT_SYMBOL (fscrypt_fname_encrypt);/** * fname_decrypt() - decrypt a filename
@@ -244,9 +245,9 @@ int fscrypt_base64_decode(const char *src, int len, u8 *dst) }EXPORT_SYMBOL (fscrypt_base64_decode); -bool fscrypt_fname_encrypted_size (const union fscrypt_policy *policy, -u32 orig_len,u32 max_len, -u32 *encrypted_len_ret) +bool __fscrypt_fname_encrypted_size (const union fscrypt_policy *policy, +u32 orig_len,u32 max_len, +u32 *encrypted_len_ret) {int padding =4 << (fscrypt_policy_flags (policy) &FSCRYPT_POLICY_FLAGS_PAD_MASK );
@@ -260,6 +261,15 @@ bool fscrypt_fname_encrypted_size(const union fscrypt_policy *policy,return true; } +bool fscrypt_fname_encrypted_size (const struct inode *inode,u32 orig_len, +u32 max_len,u32 *encrypted_len_ret) +{ +return __fscrypt_fname_encrypted_size (&inode->i_crypt_info->ci_policy, + orig_len, max_len, + encrypted_len_ret); +} +EXPORT_SYMBOL (fscrypt_fname_encrypted_size); +/** * fscrypt_fname_alloc_buffer() - allocate a buffer for presented filenames * @max_encrypted_len: maximum length of encrypted filenames the buffer will be
@@ -422,8 +432,7 @@ int fscrypt_setup_filename(struct inode *dir, const struct qstr *iname,return ret;if (fscrypt_has_encryption_key (dir)) { -if (!fscrypt_fname_encrypted_size (&dir->i_crypt_info->ci_policy, - iname->len, +if (!fscrypt_fname_encrypted_size (dir, iname->len, dir->i_sb->s_cop->max_namelen, &fname->crypto_buf.len))return -ENAMETOOLONG ;
fs/crypto/fscrypt_private.h +3 -6
@@ -292,14 +292,11 @@ void fscrypt_generate_iv(union fscrypt_iv *iv, u64 lblk_num, const struct fscrypt_info *ci);/* fname.c */ -int fscrypt_fname_encrypt (const struct inode *inode,const struct qstr *iname, -u8 *out,unsigned int olen); -bool fscrypt_fname_encrypted_size (const union fscrypt_policy *policy, -u32 orig_len,u32 max_len, -u32 *encrypted_len_ret); +bool __fscrypt_fname_encrypted_size (const union fscrypt_policy *policy, +u32 orig_len,u32 max_len, +u32 *encrypted_len_ret);/* hkdf.c */ -struct fscrypt_hkdf {struct crypto_shash *hmac_tfm; };
fs/crypto/hooks.c +3 -3
@@ -228,9 +228,9 @@ int fscrypt_prepare_symlink(struct inode *dir, const char *target,* counting it (even though it is meaningless for ciphertext) is simpler * for now since filesystems will assume it is there and subtract it. */ -if (!fscrypt_fname_encrypted_size (policy, len, - max_len -sizeof (struct fscrypt_symlink_data ), - &disk_link->len)) +if (!__fscrypt_fname_encrypted_size (policy, len, + max_len -sizeof (struct fscrypt_symlink_data ), + &disk_link->len))return -ENAMETOOLONG ; disk_link->len +=sizeof (struct fscrypt_symlink_data );
include/linux/fscrypt.h +4 -0
@@ -212,6 +212,10 @@ int fscrypt_drop_inode(struct inode *inode);/* fname.c */ int fscrypt_base64_encode (const u8 *src,int len,char *dst);int fscrypt_base64_decode (const char *src,int len,u8 *dst); +bool fscrypt_fname_encrypted_size (const struct inode *inode,u32 orig_len, +u32 max_len,u32 *encrypted_len_ret); +int fscrypt_fname_encrypt (const struct inode *inode,const struct qstr *iname, +u8 *out,unsigned int olen);int fscrypt_setup_filename (struct inode *inode,const struct qstr *iname,int lookup,struct fscrypt_name *fname);
Signature · 1 line
2.30.2
RFC PATCH v6 4/20 fscrypt: add fscrypt_context_for_new_inode
In reply to Jeff LaytonMost filesystems just call fscrypt_set_context on new inodes, which usually causes a setxattr. That's a bit late for ceph, which can send along a full blob of xattrs with the create request.
That allows us to avoid race windows that where the new inode could be seen by other clients without the crypto context attached. It also avoids the separate round trip to the server.
Refactor the code a bit to allow us to create a new crypto context, attach it to the inode, and write it to the buffer, but without calling set_context on it. ceph can later use this to marshal the context into the buffer we send along with the create request.
--- fs/crypto/policy.c | 34 ++++++++++++++++++++++++++++------ include/linux/fscrypt.h | 1 + 2 files changed, 29 insertions(+), 6 deletions(-)
fs/crypto/policy.c +28 -6
@@ -664,6 +664,31 @@ const union fscrypt_policy *fscrypt_policy_to_inherit(struct inode *dir)return fscrypt_get_dummy_policy (dir->i_sb); } +/** +* fscrypt_context_for_new_inode() - create an encryption context for a new inode +* @ctx: where context should be written +* @inode: inode from which to fetch policy and nonce +* +* Given an in-core "prepared" (via fscrypt_prepare_new_inode) inode, +* generate a new context and write it to ctx. ctx _must_ be at least +* FSCRYPT_SET_CONTEXT_MAX_SIZE bytes. +* +* Returns size of the resulting context or a negative error code. +*/ +int fscrypt_context_for_new_inode (void *ctx,struct inode *inode) +{ +struct fscrypt_info *ci = inode->i_crypt_info; + +BUILD_BUG_ON (sizeof (union fscrypt_context ) !=FSCRYPT_SET_CONTEXT_MAX_SIZE ); + +/* fscrypt_prepare_new_inode() should have set up the key already. */ +if (WARN_ON_ONCE (!ci)) +return -ENOKEY ; + +return fscrypt_new_context (ctx, &ci->ci_policy, ci->ci_nonce); +} +EXPORT_SYMBOL_GPL (fscrypt_context_for_new_inode); +/** * fscrypt_set_context() - Set the fscrypt context of a new inode * @inode: a new inode
@@ -680,12 +705,9 @@ int fscrypt_set_context(struct inode *inode, void *fs_data)union fscrypt_context ctx;int ctxsize; -/* fscrypt_prepare_new_inode() should have set up the key already. */ -if (WARN_ON_ONCE (!ci)) -return -ENOKEY ; - -BUILD_BUG_ON (sizeof (ctx) !=FSCRYPT_SET_CONTEXT_MAX_SIZE ); - ctxsize =fscrypt_new_context (&ctx, &ci->ci_policy, ci->ci_nonce); + ctxsize =fscrypt_context_for_new_inode (&ctx, inode); +if (ctxsize <0 ) +return ctxsize;/* * This may be the first time the inode number is available, so do any
include/linux/fscrypt.h +1 -0
@@ -178,6 +178,7 @@ int fscrypt_ioctl_get_policy(struct file *filp, void __user *arg);int fscrypt_ioctl_get_policy_ex (struct file *filp,void __user *arg);int fscrypt_ioctl_get_nonce (struct file *filp,void __user *arg);int fscrypt_has_permitted_context (struct inode *parent,struct inode *child); +int fscrypt_context_for_new_inode (void *ctx,struct inode *inode);int fscrypt_set_context (struct inode *inode,void *fs_data);struct fscrypt_dummy_policy {
Signature · 1 line
2.30.2
RFC PATCH v6 5/20 ceph: crypto context handling for ceph
In reply to Jeff LaytonStore the fscrypt context for an inode as an encryption.ctx xattr, and wire up the fscrypt operations to use it.
Add the decoding for the new fscrypt flag in the inode trace and set the S_ENCRYPT flag on the inode if it's set.
--- fs/ceph/Makefile | 1 + fs/ceph/crypto.c | 42 ++++++++++++++++++++++++++++++++++++++++++ fs/ceph/crypto.h | 24 ++++++++++++++++++++++++ fs/ceph/file.c | 2 ++ fs/ceph/inode.c | 6 ++++++ fs/ceph/mds_client.c | 20 ++++++++++++++++++++ fs/ceph/mds_client.h | 1 + fs/ceph/super.c | 3 +++ fs/ceph/xattr.c | 5 +++++ 9 files changed, 104 insertions(+) create mode 100644 fs/ceph/crypto.c create mode 100644 fs/ceph/crypto.h
fs/ceph/Makefile +1 -0
@@ -12,3 +12,4 @@ ceph-y := super.o inode.o dir.o file.o locks.o addr.o ioctl.o \ ceph-$(CONFIG_CEPH_FSCACHE) += cache.o ceph-$(CONFIG_CEPH_FS_POSIX_ACL) += acl.o +ceph-$(CONFIG_FS_ENCRYPTION) += crypto.o
fs/ceph/crypto.c new file +42 -0
42 lines not on this page · raw message
fs/ceph/crypto.h new file +24 -0
@@ -0,0 +1,24 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* Ceph fscrypt functionality +*/ + +#ifndef _CEPH_CRYPTO_H +#define _CEPH_CRYPTO_H + +#include <linux/fscrypt.h> + +#define CEPH_XATTR_NAME_ENCRYPTION_CONTEXT "encryption.ctx" + +#ifdef CONFIG_FS_ENCRYPTION +void ceph_fscrypt_set_ops (struct super_block *sb); + +#else /* CONFIG_FS_ENCRYPTION */ + +static inline void ceph_fscrypt_set_ops (struct super_block *sb) +{ +} + +#endif /* CONFIG_FS_ENCRYPTION */ + +#endif
fs/ceph/file.c +2 -0
@@ -595,6 +595,8 @@ static int ceph_finish_async_create(struct inode *dir, struct dentry *dentry, iinfo.xattr_data = xattr_buf;memset (iinfo.xattr_data,0 , iinfo.xattr_len); + iinfo.fscrypt =IS_ENCRYPTED (dir); + in.ino =cpu_to_le64 (vino.ino); in.snapid =cpu_to_le64 (CEPH_NOSNAP ); in.version =cpu_to_le64 (1 );// ???
fs/ceph/inode.c +6 -0
@@ -14,10 +14,12 @@#include <linux/random.h> #include <linux/sort.h> #include <linux/iversion.h> +#include <linux/fscrypt.h> #include "super.h" #include "mds_client.h" #include "cache.h" +#include "crypto.h" #include <linux/ceph/decode.h> /*
@@ -569,6 +571,7 @@ void ceph_evict_inode(struct inode *inode)clear_inode (inode);ceph_fscache_unregister_inode_cookie (ci); +fscrypt_put_encryption_info (inode);__ceph_remove_caps (ci);
@@ -951,6 +954,9 @@ int ceph_fill_inode(struct inode *inode, struct page *locked_page, xattr_blob =NULL ; } +if (iinfo->fscrypt && !IS_ENCRYPTED (inode)) +inode_set_flags (inode,S_ENCRYPTED ,S_ENCRYPTED ); +/* finally update i_version */ if (le64_to_cpu (info->version) > ci->i_version) ci->i_version =le64_to_cpu (info->version);
fs/ceph/mds_client.c +20 -0
@@ -183,6 +183,26 @@ static int parse_reply_info_in(void **p, void *end, info->rsnaps =0 ; } +if (struct_v >=5 ) { +u32 alen; + +ceph_decode_32_safe (p, end, alen, bad); + +while (alen--) { +u32 len; + +/* key */ +ceph_decode_32_safe (p, end, len, bad); +ceph_decode_skip_n (p, end, len, bad); +/* value */ +ceph_decode_32_safe (p, end, len, bad); +ceph_decode_skip_n (p, end, len, bad); + } + } + +if (struct_v >=6 ) +ceph_decode_8_safe (p, end, info->fscrypt, bad); + *p = end; }else {if (features &CEPH_FEATURE_MDS_INLINE_DATA ) {
fs/ceph/mds_client.h +1 -0
@@ -88,6 +88,7 @@ struct ceph_mds_reply_info_in {s32 dir_pin;struct ceph_timespec btime;struct ceph_timespec snap_btime; +bool fscrypt;u64 rsnaps;u64 change_attr; };
fs/ceph/super.c +3 -0
@@ -20,6 +20,7 @@#include "super.h" #include "mds_client.h" #include "cache.h" +#include "crypto.h" #include <linux/ceph/ceph_features.h> #include <linux/ceph/decode.h>
@@ -988,6 +989,8 @@ static int ceph_set_super(struct super_block *s, struct fs_context *fc) s->s_time_min =0 ; s->s_time_max =U32_MAX ; +ceph_fscrypt_set_ops (s); + ret =set_anon_super_fc (s, fc);if (ret !=0 ) fsc->sb =NULL ;
fs/ceph/xattr.c +5 -0
@@ -4,6 +4,7 @@#include "super.h" #include "mds_client.h" +#include "crypto.h" #include <linux/ceph/decode.h>
@@ -1125,6 +1126,10 @@ int __ceph_setxattr(struct inode *inode, const char *name,if (!strncmp (name,XATTR_CEPH_PREFIX ,XATTR_CEPH_PREFIX_LEN )) goto do_sync_unlocked; +/* Inform the MDS ASAP if we're setting the encryption context */ +if (!strcmp (name,CEPH_XATTR_NAME_ENCRYPTION_CONTEXT )) + goto do_sync_unlocked; +/* preallocate memory for xattr name, value, index node */ err = -ENOMEM ; newname =kmemdup (name, name_len +1 ,GFP_NOFS );
Signature · 1 line
2.30.2
RFC PATCH v6 6/20 ceph: implement -o test_dummy_encryption mount option
In reply to Jeff Layton--- fs/ceph/crypto.c | 6 ++++ fs/ceph/crypto.h | 8 +++++ fs/ceph/super.c | 77 ++++++++++++++++++++++++++++++++++++++++++++++-- fs/ceph/super.h | 7 ++++- 4 files changed, 95 insertions(+), 3 deletions(-)
fs/ceph/crypto.c +6 -0
@@ -29,9 +29,15 @@ static bool ceph_crypt_empty_dir(struct inode *inode)return ci->i_rsubdirs + ci->i_rfiles ==1 ; } +static const union fscrypt_policy *ceph_get_dummy_policy (struct super_block *sb) +{ +return ceph_sb_to_client (sb)->dummy_enc_policy.policy; +} +static struct fscrypt_operations ceph_fscrypt_ops = { .get_context = ceph_crypt_get_context, .set_context = ceph_crypt_set_context, + .get_dummy_policy = ceph_get_dummy_policy, .empty_dir = ceph_crypt_empty_dir, .max_namelen =NAME_MAX , };
fs/ceph/crypto.h +8 -0
@@ -13,12 +13,20 @@#ifdef CONFIG_FS_ENCRYPTION void ceph_fscrypt_set_ops (struct super_block *sb); +static inline void ceph_fscrypt_free_dummy_policy (struct ceph_fs_client *fsc) +{ +fscrypt_free_dummy_policy (&fsc->dummy_enc_policy); +} +#else /* CONFIG_FS_ENCRYPTION */ static inline void ceph_fscrypt_set_ops (struct super_block *sb) { } +static inline void ceph_fscrypt_free_dummy_policy (struct ceph_fs_client *fsc) +{ +}#endif /* CONFIG_FS_ENCRYPTION */ #endif
fs/ceph/super.c +75 -2
139 lines not on this page · raw message
fs/ceph/super.h +6 -1
@@ -17,6 +17,7 @@#include <linux/posix_acl.h> #include <linux/refcount.h> #include <linux/security.h> +#include <linux/fscrypt.h> #include <linux/ceph/libceph.h>
@@ -45,6 +46,7 @@#define CEPH_MOUNT_OPT_NOQUOTADF (1<<13)/* no root dir quota in statfs */ #define CEPH_MOUNT_OPT_NOCOPYFROM (1<<14)/* don't use RADOS 'copy-from' op */ #define CEPH_MOUNT_OPT_ASYNC_DIROPS (1<<15)/* allow async directory ops */ +#define CEPH_MOUNT_OPT_TEST_DUMMY_ENC (1<<16)/* enable dummy encryption (for testing) */ #define CEPH_MOUNT_OPT_DEFAULT \ (CEPH_MOUNT_OPT_DCACHE | \
@@ -97,6 +99,7 @@ struct ceph_mount_options {char *mds_namespace;/* default NULL */ char *server_path;/* default NULL (means "/") */ char *fscache_uniq;/* default NULL */ +char *test_dummy_encryption;/* default NULL */ };struct ceph_fs_client {
@@ -136,9 +139,11 @@ struct ceph_fs_client {#ifdef CONFIG_CEPH_FSCACHE struct fscache_cookie *fscache;#endif +#ifdef CONFIG_FS_ENCRYPTION +struct fscrypt_dummy_policy dummy_enc_policy; +#endif }; -/* * File i/o capability. This tracks shared state with the metadata * server that allows us to cache or writeback attributes or to read
Signature · 1 line
2.30.2
RFC PATCH v6 7/20 ceph: preallocate inode for ops that may create one
In reply to Jeff LaytonWhen creating a new inode, we need to determine the crypto context before we can transmit the RPC. The fscrypt API has a routine for getting a crypto context before a create occurs, but it requires an inode.
Change the ceph code to preallocate an inode in advance of a create of any sort (open(), mknod(), symlink(), etc). Move the existing code that generates the ACL and SELinux blobs into this routine since that's mostly common across all the different codepaths.
In most cases, we just want to allow ceph_fill_trace to use that inode after the reply comes in, so add a new field to the MDS request for it (r_new_inode).
The async create codepath is a bit different though. In that case, we want to hash the inode in advance of the RPC so that it can be used before the reply comes in. If the call subsequently fails with -EJUKEBOX, then just put the references and clean up the as_ctx. Note that with this change, we now need to regenerate the as_ctx when this occurs, but it's quite rare for it to happen.
--- fs/ceph/dir.c | 49 +++++++++++++++++------------ fs/ceph/file.c | 56 +++++++++++++++++++++------------ fs/ceph/inode.c | 74 +++++++++++++++++++++++++++++++++++++++----- fs/ceph/mds_client.c | 3 +- fs/ceph/mds_client.h | 1 + fs/ceph/super.h | 5 ++- 6 files changed, 139 insertions(+), 49 deletions(-)
fs/ceph/dir.c +29 -20
@@ -851,13 +851,6 @@ static int ceph_mknod(struct user_namespace *mnt_userns, struct inode *dir, goto out; } - err =ceph_pre_init_acls (dir, &mode, &as_ctx); -if (err <0 ) - goto out; - err =ceph_security_init_secctx (dentry, mode, &as_ctx); -if (err <0 ) - goto out; -dout ("mknod in dir %p dentry %p mode 0%ho rdev %d\n" , dir, dentry, mode, rdev); req =ceph_mdsc_create_request (mdsc,CEPH_MDS_OP_MKNOD ,USE_AUTH_MDS );
@@ -865,6 +858,14 @@ static int ceph_mknod(struct user_namespace *mnt_userns, struct inode *dir, err =PTR_ERR (req); goto out; } + + req->r_new_inode =ceph_new_inode (dir, dentry, &mode, &as_ctx); +if (IS_ERR (req->r_new_inode)) { + err =PTR_ERR (req->r_new_inode); + req->r_new_inode =NULL ; + goto out_req; + } + req->r_dentry =dget (dentry); req->r_num_caps =2 ; req->r_parent = dir;
@@ -880,6 +881,7 @@ static int ceph_mknod(struct user_namespace *mnt_userns, struct inode *dir, err =ceph_mdsc_do_request (mdsc, dir, req);if (!err && !req->r_reply_info.head->is_dentry) err =ceph_handle_notrace_create (dir, dentry); +out_req:ceph_mdsc_put_request (req); out:if (!err)
@@ -902,6 +904,7 @@ static int ceph_symlink(struct user_namespace *mnt_userns, struct inode *dir,struct ceph_mds_client *mdsc =ceph_sb_to_mdsc (dir->i_sb);struct ceph_mds_request *req;struct ceph_acl_sec_ctx as_ctx = {}; +umode_t mode =S_IFLNK |0777 ;int err;if (ceph_snap (dir) !=CEPH_NOSNAP )
@@ -912,21 +915,24 @@ static int ceph_symlink(struct user_namespace *mnt_userns, struct inode *dir, goto out; } - err =ceph_security_init_secctx (dentry,S_IFLNK |0777 , &as_ctx); -if (err <0 ) - goto out; -dout ("symlink in dir %p dentry %p to '%s'\n" , dir, dentry, dest); req =ceph_mdsc_create_request (mdsc,CEPH_MDS_OP_SYMLINK ,USE_AUTH_MDS );if (IS_ERR (req)) { err =PTR_ERR (req); goto out; } + + req->r_new_inode =ceph_new_inode (dir, dentry, &mode, &as_ctx); +if (IS_ERR (req->r_new_inode)) { + err =PTR_ERR (req->r_new_inode); + req->r_new_inode =NULL ; + goto out_req; + } + req->r_path2 =kstrdup (dest,GFP_KERNEL );if (!req->r_path2) { err = -ENOMEM ; -ceph_mdsc_put_request (req); - goto out; + goto out_req; } req->r_parent = dir;set_bit (CEPH_MDS_R_PARENT_LOCKED , &req->r_req_flags);
@@ -941,6 +947,7 @@ static int ceph_symlink(struct user_namespace *mnt_userns, struct inode *dir, err =ceph_mdsc_do_request (mdsc, dir, req);if (!err && !req->r_reply_info.head->is_dentry) err =ceph_handle_notrace_create (dir, dentry); +out_req:ceph_mdsc_put_request (req); out:if (err)
@@ -976,13 +983,6 @@ static int ceph_mkdir(struct user_namespace *mnt_userns, struct inode *dir, goto out; } - mode |=S_IFDIR ; - err =ceph_pre_init_acls (dir, &mode, &as_ctx); -if (err <0 ) - goto out; - err =ceph_security_init_secctx (dentry, mode, &as_ctx); -if (err <0 ) - goto out; req =ceph_mdsc_create_request (mdsc, op,USE_AUTH_MDS );if (IS_ERR (req)) {
@@ -990,6 +990,14 @@ static int ceph_mkdir(struct user_namespace *mnt_userns, struct inode *dir, goto out; } + mode |=S_IFDIR ; + req->r_new_inode =ceph_new_inode (dir, dentry, &mode, &as_ctx); +if (IS_ERR (req->r_new_inode)) { + err =PTR_ERR (req->r_new_inode); + req->r_new_inode =NULL ; + goto out_req; + } + req->r_dentry =dget (dentry); req->r_num_caps =2 ; req->r_parent = dir;
@@ -1006,6 +1014,7 @@ static int ceph_mkdir(struct user_namespace *mnt_userns, struct inode *dir, !req->r_reply_info.head->is_target && !req->r_reply_info.head->is_dentry) err =ceph_handle_notrace_create (dir, dentry); +out_req:ceph_mdsc_put_request (req); out:if (!err)
fs/ceph/file.c +36 -20
128 lines not on this page · raw message
fs/ceph/inode.c +67 -7
105 lines not on this page · raw message
fs/ceph/mds_client.c +2 -1
@@ -850,6 +850,7 @@ void ceph_mdsc_release_request(struct kref *kref)ceph_async_iput (req->r_parent); }ceph_async_iput (req->r_target_inode); +ceph_async_iput (req->r_new_inode);if (req->r_dentry)dput (req->r_dentry);if (req->r_old_dentry)
@@ -3263,7 +3264,7 @@ static void handle_reply(struct ceph_mds_session *session, struct ceph_msg *msg) .snap = le64_to_cpu(rinfo->targeti.in->snapid) }; - in =ceph_get_inode (mdsc->fsc->sb, tvino); + in =ceph_get_inode (mdsc->fsc->sb, tvino,xchg (&req->r_new_inode,NULL ));if (IS_ERR (in)) { err =PTR_ERR (in);mutex_lock (&session->s_mutex);
fs/ceph/mds_client.h +1 -0
@@ -262,6 +262,7 @@ struct ceph_mds_request {struct inode *r_parent;/* parent dir inode */ struct inode *r_target_inode;/* resulting inode */ +struct inode *r_new_inode;/* new inode (for creates) */ #define CEPH_MDS_R_DIRECT_IS_HASH (1)/* r_direct_hash is valid */ #define CEPH_MDS_R_ABORTED (2)/* call was aborted */
fs/ceph/super.h +4 -1
@@ -961,6 +961,7 @@ static inline bool __ceph_have_pending_cap_snap(struct ceph_inode_info *ci)/* inode.c */ struct ceph_mds_reply_info_in ;struct ceph_mds_reply_dirfrag ; +struct ceph_acl_sec_ctx ;extern const struct inode_operations ceph_file_iops;
@@ -968,8 +969,10 @@ extern struct inode *ceph_alloc_inode(struct super_block *sb);extern void ceph_evict_inode (struct inode *inode);extern void ceph_free_inode (struct inode *inode); +struct inode *ceph_new_inode (struct inode *dir,struct dentry *dentry, +umode_t *mode,struct ceph_acl_sec_ctx *as_ctx);extern struct inode *ceph_get_inode (struct super_block *sb, -struct ceph_vino vino); +struct ceph_vino vino,struct inode *newino);extern struct inode *ceph_get_snapdir (struct inode *parent);extern int ceph_fill_file_size (struct inode *inode,int issued,u32 truncate_seq,u64 truncate_size,u64 size);
Signature · 1 line
2.30.2
RFC PATCH v6 8/20 ceph: add routine to create fscrypt context prior to RPC
In reply to Jeff LaytonAfter pre-creating a new inode, do an fscrypt prepare on it, fetch a new encryption context and then marshal that into the security context to be sent along with the RPC. Call the new function from ceph_new_inode.
--- fs/ceph/crypto.c | 61 ++++++++++++++++++++++++++++++++++++++++++++++++ fs/ceph/crypto.h | 12 ++++++++++ fs/ceph/inode.c | 9 +++++-- fs/ceph/super.h | 3 +++ 4 files changed, 83 insertions(+), 2 deletions(-)
fs/ceph/crypto.c +61 -0
@@ -46,3 +46,64 @@ void ceph_fscrypt_set_ops(struct super_block *sb) {fscrypt_set_ops (sb, &ceph_fscrypt_ops); } + +int ceph_fscrypt_prepare_context (struct inode *dir,struct inode *inode, +struct ceph_acl_sec_ctx *as) +{ +int ret, ctxsize; +size_t name_len; +char *name; +struct ceph_pagelist *pagelist = as->pagelist; +bool encrypted = false; + + ret =fscrypt_prepare_new_inode (dir, inode, &encrypted); +if (ret) +return ret; +if (!encrypted) +return 0 ; + + inode->i_flags |=S_ENCRYPTED ; + + ctxsize =fscrypt_context_for_new_inode (&as->fscrypt, inode); +if (ctxsize <0 ) +return ctxsize; + +/* marshal it in page array */ +if (!pagelist) { + pagelist =ceph_pagelist_alloc (GFP_KERNEL ); +if (!pagelist) +return -ENOMEM ; + ret =ceph_pagelist_reserve (pagelist,PAGE_SIZE ); +if (ret) + goto out; +ceph_pagelist_encode_32 (pagelist,1 ); + } + + name =CEPH_XATTR_NAME_ENCRYPTION_CONTEXT ; + name_len =strlen (name); + ret =ceph_pagelist_reserve (pagelist,4 *2 + name_len + ctxsize); +if (ret) + goto out; + +if (as->pagelist) { +BUG_ON (pagelist->length <=sizeof (__le32)); +if (list_is_singular (&pagelist->head)) { +le32_add_cpu ((__le32 *)pagelist->mapped_tail,1 ); + }else { +struct page *page =list_first_entry (&pagelist->head, + struct page, lru); +void *addr =kmap_atomic (page); +le32_add_cpu ((__le32 *)addr,1 ); +kunmap_atomic (addr); + } + } + +ceph_pagelist_encode_32 (pagelist, name_len); +ceph_pagelist_append (pagelist, name, name_len); +ceph_pagelist_encode_32 (pagelist, ctxsize); +ceph_pagelist_append (pagelist, as->fscrypt, ctxsize); +out: +if (pagelist && !as->pagelist) +ceph_pagelist_release (pagelist); +return ret; +}
fs/ceph/crypto.h +12 -0
@@ -18,6 +18,9 @@ static inline void ceph_fscrypt_free_dummy_policy(struct ceph_fs_client *fsc) fscrypt_free_dummy_policy(&fsc->dummy_enc_policy); } +int ceph_fscrypt_prepare_context (struct inode *dir,struct inode *inode, +struct ceph_acl_sec_ctx *as); +#else /* CONFIG_FS_ENCRYPTION */ static inline void ceph_fscrypt_set_ops (struct super_block *sb)
@@ -27,6 +30,15 @@ static inline void ceph_fscrypt_set_ops(struct super_block *sb)static inline void ceph_fscrypt_free_dummy_policy (struct ceph_fs_client *fsc) { } + +static inline int ceph_fscrypt_prepare_context (struct inode *dir,struct inode *inode, +struct ceph_acl_sec_ctx *as) +{ +if (IS_ENCRYPTED (dir)) +return -EOPNOTSUPP ; +return 0 ; +} +#endif /* CONFIG_FS_ENCRYPTION */ #endif
fs/ceph/inode.c +7 -2
@@ -83,12 +83,17 @@ struct inode *ceph_new_inode(struct inode *dir, struct dentry *dentry, goto out_err; } + inode->i_state =0 ; + inode->i_mode = *mode; + err =ceph_security_init_secctx (dentry, *mode, as_ctx);if (err <0 ) goto out_err; - inode->i_state =0 ; - inode->i_mode = *mode; + err =ceph_fscrypt_prepare_context (dir, inode, as_ctx); +if (err) + goto out_err; +return inode; out_err:iput (inode);
fs/ceph/super.h +3 -0
@@ -1055,6 +1055,9 @@ struct ceph_acl_sec_ctx {#ifdef CONFIG_CEPH_FS_SECURITY_LABEL void *sec_ctx;u32 sec_ctxlen; +#endif +#ifdef CONFIG_FS_ENCRYPTION +u8 fscrypt[FSCRYPT_SET_CONTEXT_MAX_SIZE ];#endif struct ceph_pagelist *pagelist; };
Signature · 1 line
2.30.2
RFC PATCH v6 9/20 ceph: make ceph_msdc_build_path use ref-walk
In reply to Jeff LaytonEncryption potentially requires allocation, at which point we'll need to be in a non-atomic context. Convert ceph_msdc_build_path to take dentry spinlocks and references instead of using rcu_read_lock to walk the path.
This is slightly less efficient, and we may want to eventually allow using RCU when the leaf dentry isn't encrypted.
--- fs/ceph/mds_client.c | 35 +++++++++++++++++++---------------- 1 file changed, 19 insertions(+), 16 deletions(-)
fs/ceph/mds_client.c +19 -16
@@ -2357,7 +2357,8 @@ static inline u64 __get_oldest_tid(struct ceph_mds_client *mdsc)char *ceph_mdsc_build_path (struct dentry *dentry,int *plen,u64 *pbase,int stop_on_nosnap) { -struct dentry *temp; +struct dentry *cur; +struct inode *inode;char *path;int pos;unsigned seq;
@@ -2374,34 +2375,35 @@ char *ceph_mdsc_build_path(struct dentry *dentry, int *plen, u64 *pbase, path[pos] ='\0' ; seq =read_seqbegin (&rename_lock); -rcu_read_lock (); - temp = dentry; + cur =dget (dentry);for (;;) { -struct inode *inode; +struct dentry *temp; -spin_lock (&temp->d_lock); - inode =d_inode (temp); +spin_lock (&cur->d_lock); + inode =d_inode (cur);if (inode &&ceph_snap (inode) ==CEPH_SNAPDIR ) {dout ("build_path path+%d: %p SNAPDIR\n" , - pos, temp); - }else if (stop_on_nosnap && inode && dentry != temp && + pos, cur); + }else if (stop_on_nosnap && inode && dentry != cur &&ceph_snap (inode) ==CEPH_NOSNAP ) { -spin_unlock (&temp->d_lock); +spin_unlock (&cur->d_lock); pos++;/* get rid of any prepended '/' */ break ; }else { - pos -= temp->d_name.len; + pos -= cur->d_name.len;if (pos <0 ) { -spin_unlock (&temp->d_lock); +spin_unlock (&cur->d_lock);break ; } -memcpy (path + pos, temp->d_name.name, temp->d_name.len); +memcpy (path + pos, cur->d_name.name, cur->d_name.len); } + temp = cur;spin_unlock (&temp->d_lock); - temp =READ_ONCE (temp->d_parent); + cur =dget_parent (temp); +dput (temp);/* Are we at the root? */ -if (IS_ROOT (temp)) +if (IS_ROOT (cur))break ;/* Are we out of buffer? */
@@ -2410,8 +2412,9 @@ char *ceph_mdsc_build_path(struct dentry *dentry, int *plen, u64 *pbase, path[pos] ='/' ; } - base =ceph_ino (d_inode (temp)); -rcu_read_unlock (); + inode =d_inode (cur); + base = inode ?ceph_ino (inode) :0 ; +dput (cur);if (read_seqretry (&rename_lock, seq)) goto retry;
Signature · 1 line
2.30.2
RFC PATCH v6 10/20 ceph: add encrypted fname handling to ceph_mdsc_build_path
In reply to Jeff LaytonAllow ceph_mdsc_build_path to encrypt and base64 encode the filename when the parent is encrypted and we're sending the path to the MDS.
In most cases, we just encrypt the filenames and base64 encode them, but when the name is longer than CEPH_NOHASH_NAME_MAX, we use a similar scheme to fscrypt proper, and hash the remaning bits with sha256.
When doing this, we then send along the full crypttext of the name in the new alternate_name field of the MClientRequest. The MDS can then send that along in readdir responses and traces.
--- fs/ceph/crypto.h | 16 +++++ fs/ceph/mds_client.c | 138 +++++++++++++++++++++++++++++++++++++------ 2 files changed, 136 insertions(+), 18 deletions(-)
fs/ceph/crypto.h +16 -0
@@ -6,11 +6,27 @@#ifndef _CEPH_CRYPTO_H#define _CEPH_CRYPTO_H +#include <crypto/sha2.h> #include <linux/fscrypt.h> #define CEPH_XATTR_NAME_ENCRYPTION_CONTEXT "encryption.ctx"#ifdef CONFIG_FS_ENCRYPTION + +/* +* We want to encrypt filenames when creating them, but the encrypted +* versions of those names may have illegal characters in them. To mitigate +* that, we base64 encode them, but that gives us a result that can exceed +* NAME_MAX. +* +* Follow a similar scheme to fscrypt itself, and cap the filename to a +* smaller size. If the cleartext name is longer than the value below, then +* sha256 hash the remaining bytes. +* +* 189 bytes => 252 bytes base64-encoded, which is <= NAME_MAX (255) +*/ +#define CEPH_NOHASH_NAME_MAX (189 - SHA256_DIGEST_SIZE) +void ceph_fscrypt_set_ops (struct super_block *sb);static inline void ceph_fscrypt_free_dummy_policy (struct ceph_fs_client *fsc)
fs/ceph/mds_client.c +120 -18
189 lines not on this page · raw message
Signature · 1 line
2.30.2
RFC PATCH v6 11/20 ceph: decode alternate_name in lease info
In reply to Jeff LaytonCeph is a bit different from local filesystems, in that we don't want to store filenames as raw binary data, since we may also be dealing with clients that don't support fscrypt.
We could just base64-encode the encrypted filenames, but that could leave us with filenames longer than NAME_MAX. It turns out that the MDS doesn't care much about filename length, but the clients do.
To manage this, we've added a new "alternate name" field that can be optionally added to any dentry that we'll use to store the binary crypttext of the filename if its base64-encoded value will be longer than NAME_MAX. When a dentry has one of these names attached, the MDS will send it along in the lease info, which we can then store for later usage.
--- fs/ceph/mds_client.c | 40 ++++++++++++++++++++++++++++++---------- fs/ceph/mds_client.h | 11 +++++++---- 2 files changed, 37 insertions(+), 14 deletions(-)
fs/ceph/mds_client.c +30 -10
@@ -283,27 +283,44 @@ static int parse_reply_info_dir(void **p, void *end,static int parse_reply_info_lease (void **p,void *end,struct ceph_mds_reply_lease **lease, -u64 features) +u64 features,u32 *altname_len,u8 **altname) { +u8 struct_v; +u32 struct_len; +if (features == (u64)-1 ) { -u8 struct_v, struct_compat; -u32 struct_len; +u8 struct_compat; +ceph_decode_8_safe (p, end, struct_v, bad);ceph_decode_8_safe (p, end, struct_compat, bad); +/* struct_v is expected to be >= 1. we only understand * encoding whose struct_compat == 1. */ if (!struct_v || struct_compat !=1 ) goto bad; +ceph_decode_32_safe (p, end, struct_len, bad); -ceph_decode_need (p, end, struct_len, bad); - end = *p + struct_len; + }else { + struct_len =sizeof (**lease); + *altname_len =0 ; + *altname =NULL ; } -ceph_decode_need (p, end,sizeof (**lease), bad); +ceph_decode_need (p, end, struct_len, bad); *lease = *p; *p +=sizeof (**lease); -if (features == (u64)-1 ) - *p = end; + +if (features == (u64)-1 ) { +if (struct_v >=2 ) { +ceph_decode_32_safe (p, end, *altname_len, bad); +ceph_decode_need (p, end, *altname_len, bad); + *altname = *p; + *p += *altname_len; + }else { + *altname =NULL ; + *altname_len =0 ; + } + }return 0 ; bad:return -EIO ;
@@ -333,7 +350,8 @@ static int parse_reply_info_trace(void **p, void *end, info->dname = *p; *p += info->dname_len; - err =parse_reply_info_lease (p, end, &info->dlease, features); + err =parse_reply_info_lease (p, end, &info->dlease, features, + &info->altname_len, &info->altname);if (err <0 ) goto out_bad; }
@@ -400,9 +418,11 @@ static int parse_reply_info_readdir(void **p, void *end,dout ("parsed dir dname '%.*s'\n" , rde->name_len, rde->name);/* dentry lease */ - err =parse_reply_info_lease (p, end, &rde->lease, features); + err =parse_reply_info_lease (p, end, &rde->lease, features, + &rde->altname_len, &rde->altname);if (err) goto out_bad; +/* inode */ err =parse_reply_info_in (p, end, &rde->inode, features);if (err <0 )
fs/ceph/mds_client.h +7 -4
@@ -29,8 +29,8 @@ enum ceph_feature_type {CEPHFS_FEATURE_MULTI_RECONNECT ,CEPHFS_FEATURE_DELEG_INO ,CEPHFS_FEATURE_METRIC_COLLECT , - - CEPHFS_FEATURE_MAX = CEPHFS_FEATURE_METRIC_COLLECT, +CEPHFS_FEATURE_ALTERNATE_NAME , + CEPHFS_FEATURE_MAX = CEPHFS_FEATURE_ALTERNATE_NAME, };/*
@@ -45,8 +45,7 @@ enum ceph_feature_type {CEPHFS_FEATURE_MULTI_RECONNECT , \CEPHFS_FEATURE_DELEG_INO , \CEPHFS_FEATURE_METRIC_COLLECT , \ - \ -CEPHFS_FEATURE_MAX , \ +CEPHFS_FEATURE_ALTERNATE_NAME , \ } #define CEPHFS_FEATURES_CLIENT_REQUIRED {}
@@ -95,7 +94,9 @@ struct ceph_mds_reply_info_in {struct ceph_mds_reply_dir_entry {char *name; +u8 *altname;u32 name_len; +u32 altname_len;struct ceph_mds_reply_lease *lease;struct ceph_mds_reply_info_in inode;loff_t offset;
@@ -114,7 +115,9 @@ struct ceph_mds_reply_info_parsed {struct ceph_mds_reply_info_in diri, targeti;struct ceph_mds_reply_dirfrag *dirfrag;char *dname; +u8 *altname;u32 dname_len; +u32 altname_len;struct ceph_mds_reply_lease *dlease;/* extra */
Signature · 1 line
2.30.2
RFC PATCH v6 12/20 ceph: send altname in MClientRequest
In reply to Jeff LaytonIn the event that we have a filename longer than CEPH_NOHASH_NAME_MAX, we'll need to hash the tail of the filename. The client however will still need to know the full name of the file if it has a key.
To support this, the MClientRequest field has grown a new alternate_name field that we populate with the full (binary) crypttext of the filename. This is then transmitted to the clients in readdir or traces as part of the dentry lease.
Add support for populating this field when the filenames are very long.
--- fs/ceph/mds_client.c | 79 +++++++++++++++++++++++++++++++++++++++++--- fs/ceph/mds_client.h | 2 ++ 2 files changed, 76 insertions(+), 5 deletions(-)
fs/ceph/mds_client.c +74 -5
@@ -892,6 +892,7 @@ void ceph_mdsc_release_request(struct kref *kref)put_cred (req->r_cred);if (req->r_pagelist)ceph_pagelist_release (req->r_pagelist); +kfree (req->r_altname);put_request_session (req);ceph_unreserve_caps (req->r_mdsc, &req->r_caps_reservation);WARN_ON_ONCE (!list_empty (&req->r_wait));
@@ -2416,11 +2417,66 @@ static int encode_encrypted_fname(const struct inode *parent, struct dentry *dendout ("base64-encoded ciphertext name = %.*s\n" , len, buf);return elen; } + +static u8 *get_fscrypt_altname (const struct ceph_mds_request *req,u32 *plen) +{ +struct inode *dir = req->r_parent; +struct dentry *dentry = req->r_dentry; +u8 *cryptbuf =NULL ; +u32 len =0 ; +int ret =0 ; + +/* only encode if we have parent and dentry */ +if (!dir || !dentry) + goto success; + +/* No-op unless this is encrypted */ +if (!IS_ENCRYPTED (dir)) + goto success; + + ret =__fscrypt_prepare_readdir (dir); +if (ret) +return ERR_PTR (ret); + +/* No key? Just ignore it. */ +if (!fscrypt_has_encryption_key (dir)) + goto success; + +if (!fscrypt_fname_encrypted_size (dir, dentry->d_name.len,NAME_MAX , &len)) { +WARN_ON_ONCE (1 ); +return ERR_PTR (-ENAMETOOLONG ); + } + +/* No need to append altname if name is short enough */ +if (len <=CEPH_NOHASH_NAME_MAX ) { + len =0 ; + goto success; + } + + cryptbuf =kmalloc (len,GFP_KERNEL ); +if (!cryptbuf) +return ERR_PTR (-ENOMEM ); + + ret =fscrypt_fname_encrypt (dir, &dentry->d_name, cryptbuf, len); +if (ret) { +kfree (cryptbuf); +return ERR_PTR (ret); + } +success: + *plen = len; +return cryptbuf; +}#else static int encode_encrypted_fname (const struct inode *parent,struct dentry *dentry,char *buf) {return -EOPNOTSUPP ; } + +static u8 *get_fscrypt_altname (const struct ceph_mds_request *req,u32 *plen) +{ + *plen =0 ; +return NULL ; +}#endif /**
@@ -2635,7 +2691,7 @@ static int set_request_path_attr(struct inode *rinode, struct dentry *rdentry,return r; } -static void encode_timestamp_and_gids (void **p, +static void encode_mclientrequest_tail (void **p,const struct ceph_mds_request *req) {struct ceph_timespec ts;
@@ -2644,11 +2700,16 @@ static void encode_timestamp_and_gids(void **p,ceph_encode_timespec64 (&ts, &req->r_stamp);ceph_encode_copy (p, &ts,sizeof (ts)); -/* gid_list */ +/* v4: gid_list */ ceph_encode_32 (p, req->r_cred->group_info->ngroups);for (i =0 ; i < req->r_cred->group_info->ngroups; i++)ceph_encode_64 (p,from_kgid (&init_user_ns, req->r_cred->group_info->gid[i])); + +/* v5: altname */ +ceph_encode_32 (p, req->r_altname_len); +if (req->r_altname_len) +ceph_encode_copy (p, req->r_altname, req->r_altname_len); }/*
@@ -2693,10 +2754,18 @@ static struct ceph_msg *create_request_message(struct ceph_mds_session *session, goto out_free1; } + req->r_altname =get_fscrypt_altname (req, &req->r_altname_len); +if (IS_ERR (req->r_altname)) { + msg =ERR_CAST (req->r_altname); + req->r_altname =NULL ; + goto out_free2; + } + len = legacy ?sizeof (*head) :sizeof (struct ceph_mds_request_head ); len += pathlen1 + pathlen2 +2 *(1 +sizeof (u32) +sizeof (u64)) +sizeof (struct ceph_timespec ); len +=sizeof (u32) + (sizeof (u64) * req->r_cred->group_info->ngroups); + len +=sizeof (u32) + req->r_altname_len;/* calculate (max) length for cap releases */ len += sizeof(struct ceph_mds_request_release) *
@@ -2727,7 +2796,7 @@ static struct ceph_msg *create_request_message(struct ceph_mds_session *session, }else {struct ceph_mds_request_head *new_head = msg->front.iov_base; - msg->hdr.version =cpu_to_le16 (4 ); + msg->hdr.version =cpu_to_le16 (5 ); new_head->version =cpu_to_le16 (CEPH_MDS_REQUEST_HEAD_VERSION ); head = (struct ceph_mds_request_head_old *)&new_head->oldest_client_tid; p = msg->front.iov_base +sizeof (*new_head);
@@ -2778,7 +2847,7 @@ static struct ceph_msg *create_request_message(struct ceph_mds_session *session, head->num_releases =cpu_to_le16 (releases); -encode_timestamp_and_gids (&p, req); +encode_mclientrequest_tail (&p, req);if (WARN_ON_ONCE (p > end)) {ceph_msg_put (msg);
@@ -2887,7 +2956,7 @@ static int __prepare_send_request(struct ceph_mds_session *session, rhead->num_releases =0 ; p = msg->front.iov_base + req->r_request_release_offset; -encode_timestamp_and_gids (&p, req); +encode_mclientrequest_tail (&p, req); msg->front.iov_len = p - msg->front.iov_base; msg->hdr.front_len =cpu_to_le32 (msg->front.iov_len);
fs/ceph/mds_client.h +2 -0
@@ -280,6 +280,8 @@ struct ceph_mds_request {struct mutex r_fill_mutex;union ceph_mds_request_args r_args; +u8 *r_altname;/* fscrypt binary crypttext for long filenames */ +u32 r_altname_len;/* length of r_altname */ int r_fmode;/* file mode, if expecting cap */ const struct cred *r_cred;int r_request_release_offset;
Signature · 1 line
2.30.2
RFC PATCH v6 13/20 ceph: properly set DCACHE_NOKEY_NAME flag in lookup
In reply to Jeff LaytonThis is required so that we know to invalidate these dentries when the directory is unlocked.
--- fs/ceph/dir.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
fs/ceph/dir.c +11 -0
@@ -755,6 +755,17 @@ static struct dentry *ceph_lookup(struct inode *dir, struct dentry *dentry,if (dentry->d_name.len >NAME_MAX )return ERR_PTR (-ENAMETOOLONG ); +if (IS_ENCRYPTED (dir)) { + err =__fscrypt_prepare_readdir (dir); +if (err) +return ERR_PTR (err); +if (!fscrypt_has_encryption_key (dir)) { +spin_lock (&dentry->d_lock); + dentry->d_flags |=DCACHE_NOKEY_NAME ; +spin_unlock (&dentry->d_lock); + } + } +/* can we conclude ENOENT locally? */ if (d_really_is_negative (dentry)) {struct ceph_inode_info *ci =ceph_inode (dir);
Signature · 1 line
2.30.2
RFC PATCH v6 14/20 ceph: make d_revalidate call fscrypt revalidator for encrypted dentries
In reply to Jeff LaytonIf we have a dentry which represents a no-key name, then we need to test whether the parent directory's encryption key has since been added. Do that before we test anything else about the dentry.
--- fs/ceph/dir.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
fs/ceph/dir.c +6 -2
@@ -1697,6 +1697,10 @@ static int ceph_d_revalidate(struct dentry *dentry, unsigned int flags)struct inode *dir, *inode;struct ceph_mds_client *mdsc; + valid =fscrypt_d_revalidate (dentry, flags); +if (valid <=0 ) +return valid; +if (flags &LOOKUP_RCU ) { parent =READ_ONCE (dentry->d_parent); dir =d_inode_rcu (parent);
@@ -1709,8 +1713,8 @@ static int ceph_d_revalidate(struct dentry *dentry, unsigned int flags) inode =d_inode (dentry); } -dout ("d_revalidate %p '%pd' inode %p offset 0x%llx\n" , dentry, - dentry, inode,ceph_dentry (dentry)->offset); +dout ("d_revalidate %p '%pd' inode %p offset 0x%llx nokey %d\n" , dentry, + dentry, inode,ceph_dentry (dentry)->offset, !!(dentry->d_flags &DCACHE_NOKEY_NAME )); mdsc =ceph_sb_to_client (dir->i_sb)->mdsc;
Signature · 1 line
2.30.2
RFC PATCH v6 15/20 ceph: add helpers for converting names for userland presentation
In reply to Jeff Layton--- fs/ceph/crypto.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++ fs/ceph/crypto.h | 41 ++++++++++++++++++++++++++ 2 files changed, 117 insertions(+)
fs/ceph/crypto.c +76 -0
@@ -107,3 +107,79 @@ int ceph_fscrypt_prepare_context(struct inode *dir, struct inode *inode,ceph_pagelist_release (pagelist);return ret; } + +/** +* ceph_fname_to_usr - convert a filename for userland presentation +* @fname: ceph_fname to be converted +* @tname: temporary name buffer to use for conversion (may be NULL) +* @oname: where converted name should be placed +* @is_nokey: set to true if key wasn't available during conversion (may be NULL) +* +* Given a filename (usually from the MDS), format it for presentation to +* userland. If @parent is not encrypted, just pass it back as-is. +* +* Otherwise, base64 decode the string, and then ask fscrypt to format it +* for userland presentation. +* +* Returns 0 on success or negative error code on error. +*/ +int ceph_fname_to_usr (const struct ceph_fname *fname,struct fscrypt_str *tname, +struct fscrypt_str *oname,bool *is_nokey) +{ +int ret; +struct fscrypt_str _tname =FSTR_INIT (NULL ,0 ); +struct fscrypt_str iname; + +if (!IS_ENCRYPTED (fname->dir)) { + oname->name = fname->name; + oname->len = fname->name_len; +return 0 ; + } + +/* Sanity check that the resulting name will fit in the buffer */ +if (fname->name_len >FSCRYPT_BASE64_CHARS (NAME_MAX )) +return -EIO ; + + ret =__fscrypt_prepare_readdir (fname->dir); +if (ret) +return ret; + +/* +* Use the raw dentry name as sent by the MDS instead of +* generating a nokey name via fscrypt. +*/ +if (!fscrypt_has_encryption_key (fname->dir)) { +memcpy (oname->name, fname->name, fname->name_len); + oname->len = fname->name_len; +if (is_nokey) + *is_nokey = true; +return 0 ; + } + +if (fname->ctext_len ==0 ) { +int declen; + +if (!tname) { + ret =fscrypt_fname_alloc_buffer (NAME_MAX , &_tname); +if (ret) +return ret; + tname = &_tname; + } + + declen =fscrypt_base64_decode (fname->name, fname->name_len, tname->name); +if (declen <=0 ) { + ret = -EIO ; + goto out; + } + iname.name = tname->name; + iname.len = declen; + }else { + iname.name = fname->ctext; + iname.len = fname->ctext_len; + } + + ret =fscrypt_fname_disk_to_usr (fname->dir,0 ,0 , &iname, oname); +out: +fscrypt_fname_free_buffer (&_tname); +return ret; +}
fs/ceph/crypto.h +41 -0
59 lines not on this page · raw message
Signature · 1 line
2.30.2
RFC PATCH v6 16/20 ceph: add fscrypt support to ceph_fill_trace
In reply to Jeff LaytonWhen we get a dentry in a trace, decrypt the name so we can properly instantiate the dentry.
--- fs/ceph/inode.c | 30 ++++++++++++++++++++++++++++-- 1 file changed, 28 insertions(+), 2 deletions(-)
fs/ceph/inode.c +28 -2
@@ -1377,8 +1377,15 @@ int ceph_fill_trace(struct super_block *sb, struct ceph_mds_request *req)if (dir && req->r_op ==CEPH_MDS_OP_LOOKUPNAME &&test_bit (CEPH_MDS_R_PARENT_LOCKED , &req->r_req_flags) && !test_bit (CEPH_MDS_R_ABORTED , &req->r_req_flags)) { +bool is_nokey = false;struct qstr dname;struct dentry *dn, *parent; +struct fscrypt_str oname =FSTR_INIT (NULL ,0 ); +struct ceph_fname fname = { .dir = dir, + .name = rinfo->dname, + .ctext = rinfo->altname, + .name_len = rinfo->dname_len, + .ctext_len = rinfo->altname_len };BUG_ON (!rinfo->head->is_target);BUG_ON (req->r_dentry);
@@ -1386,8 +1393,20 @@ int ceph_fill_trace(struct super_block *sb, struct ceph_mds_request *req) parent =d_find_any_alias (dir);BUG_ON (!parent); - dname.name = rinfo->dname; - dname.len = rinfo->dname_len; + err =ceph_fname_alloc_buffer (dir, &oname); +if (err <0 ) { +dput (parent); + goto done; + } + + err =ceph_fname_to_usr (&fname,NULL , &oname, &is_nokey); +if (err <0 ) { +dput (parent); +ceph_fname_free_buffer (dir, &oname); + goto done; + } + dname.name = oname.name; + dname.len = oname.len; dname.hash =full_name_hash (parent, dname.name, dname.len); tvino.ino =le64_to_cpu (rinfo->targeti.in->ino); tvino.snap =le64_to_cpu (rinfo->targeti.in->snapid);
@@ -1402,9 +1421,15 @@ int ceph_fill_trace(struct super_block *sb, struct ceph_mds_request *req) dname.len, dname.name, dn);if (!dn) {dput (parent); +ceph_fname_free_buffer (dir, &oname); err = -ENOMEM ; goto done; } +if (is_nokey) { +spin_lock (&dn->d_lock); + dn->d_flags |=DCACHE_NOKEY_NAME ; +spin_unlock (&dn->d_lock); + } err =0 ; } else if (d_really_is_positive(dn) && (ceph_ino(d_inode(dn)) != tvino.ino ||
@@ -1416,6 +1441,7 @@ int ceph_fill_trace(struct super_block *sb, struct ceph_mds_request *req)dput (dn); goto retry_lookup; } +ceph_fname_free_buffer (dir, &oname); req->r_dentry = dn;dput (parent);
Signature · 1 line
2.30.2
RFC PATCH v6 17/20 ceph: add support to readdir for encrypted filenames
In reply to Jeff LaytonAdd helper functions for buffer management and for decrypting filenames returned by the MDS. Wire those into the readdir codepaths.
--- fs/ceph/dir.c | 62 +++++++++++++++++++++++++++++++++++++++---------- fs/ceph/inode.c | 38 +++++++++++++++++++++++++++--- 2 files changed, 85 insertions(+), 15 deletions(-)
fs/ceph/dir.c +50 -12
@@ -9,6 +9,7 @@#include "super.h" #include "mds_client.h" +#include "crypto.h" /* * Directory operations: readdir, lookup, create, link, unlink,
@@ -241,7 +242,9 @@ static int __dcache_readdir(struct file *file, struct dir_context *ctx, di =ceph_dentry (dentry);if (d_unhashed (dentry) ||d_really_is_negative (dentry) || - di->lease_shared_gen != shared_gen) { + di->lease_shared_gen != shared_gen || + ((dentry->d_flags &DCACHE_NOKEY_NAME ) && +fscrypt_has_encryption_key (dir))) {spin_unlock (&dentry->d_lock);dput (dentry); err = -EAGAIN ;
@@ -313,6 +316,8 @@ static int ceph_readdir(struct file *file, struct dir_context *ctx)int err;unsigned frag =-1 ;struct ceph_mds_reply_info_parsed *rinfo; +struct fscrypt_str tname =FSTR_INIT (NULL ,0 ); +struct fscrypt_str oname =FSTR_INIT (NULL ,0 );dout ("readdir %p file %p pos %llx\n" , inode, file, ctx->pos);if (dfi->file_info.flags &CEPH_F_ATEND )
@@ -340,6 +345,10 @@ static int ceph_readdir(struct file *file, struct dir_context *ctx) ctx->pos =2 ; } + err =fscrypt_prepare_readdir (inode); +if (err) + goto out; +spin_lock (&ci->i_ceph_lock);/* request Fx cap. if have Fx, we don't need to release Fs cap * for later create/unlink. */
@@ -360,6 +369,14 @@ static int ceph_readdir(struct file *file, struct dir_context *ctx)spin_unlock (&ci->i_ceph_lock); } + err =ceph_fname_alloc_buffer (inode, &tname); +if (err <0 ) + goto out; + + err =ceph_fname_alloc_buffer (inode, &oname); +if (err <0 ) + goto out; +/* proceed with a normal readdir */ more:/* do we have the correct frag content buffered? */
@@ -387,12 +404,14 @@ static int ceph_readdir(struct file *file, struct dir_context *ctx)dout ("readdir fetching %llx.%llx frag %x offset '%s'\n" ,ceph_vinop (inode), frag, dfi->last_name); req =ceph_mdsc_create_request (mdsc, op,USE_AUTH_MDS ); -if (IS_ERR (req)) -return PTR_ERR (req); +if (IS_ERR (req)) { + err =PTR_ERR (req); + goto out; + } err =ceph_alloc_readdir_reply_buffer (req, inode);if (err) {ceph_mdsc_put_request (req); -return err; + goto out; }/* hints to request -> mds selection code */ req->r_direct_mode =USE_AUTH_MDS ;
@@ -405,7 +424,8 @@ static int ceph_readdir(struct file *file, struct dir_context *ctx) req->r_path2 =kstrdup (dfi->last_name,GFP_KERNEL );if (!req->r_path2) {ceph_mdsc_put_request (req); -return -ENOMEM ; + err = -ENOMEM ; + goto out; } }else if (is_hash_order (ctx->pos)) { req->r_args.readdir.offset_hash =
@@ -426,7 +446,7 @@ static int ceph_readdir(struct file *file, struct dir_context *ctx) err =ceph_mdsc_do_request (mdsc,NULL , req);if (err <0 ) {ceph_mdsc_put_request (req); -return err; + goto out; } dout("readdir got and parsed readdir result=%d on " "frag %x, end=%d, complete=%d, hash_order=%d\n",
@@ -479,7 +499,7 @@ static int ceph_readdir(struct file *file, struct dir_context *ctx) err =note_last_dentry (dfi, rde->name, rde->name_len, next_offset);if (err) -return err; + goto out; }else if (req->r_reply_info.dir_end) { dfi->next_offset =2 ;/* keep last name */
@@ -507,22 +527,37 @@ static int ceph_readdir(struct file *file, struct dir_context *ctx) }for (; i < rinfo->dir_nr; i++) {struct ceph_mds_reply_dir_entry *rde = rinfo->dir_entries + i; +struct ceph_fname fname = { .dir = inode, + .name = rde->name, + .name_len = rde->name_len, + .ctext = rde->altname, + .ctext_len = rde->altname_len }; +u32 olen = oname.len;BUG_ON (rde->offset < ctx->pos); +BUG_ON (!rde->inode.in); ctx->pos = rde->offset;dout ("readdir (%d/%d) -> %llx '%.*s' %p\n" , i, rinfo->dir_nr, ctx->pos, rde->name_len, rde->name, &rde->inode.in); -BUG_ON (!rde->inode.in); + err =ceph_fname_to_usr (&fname, &tname, &oname,NULL ); +if (err) { +dout ("Unable to decode %.*s. Skipping it.\n" , rde->name_len, rde->name); +continue ; + } -if (!dir_emit (ctx, rde->name, rde->name_len, +if (!dir_emit (ctx, oname.name, oname.len,ceph_present_ino (inode->i_sb,le64_to_cpu (rde->inode.in->ino)),le32_to_cpu (rde->inode.in->mode) >>12 )) {dout ("filldir stopping us...\n" ); -return 0 ; + err =0 ; + goto out; } + +/* Reset the lengths to their original allocated vals */ + oname.len = olen; ctx->pos++; }
@@ -577,9 +612,12 @@ static int ceph_readdir(struct file *file, struct dir_context *ctx) dfi->dir_ordered_count);spin_unlock (&ci->i_ceph_lock); } - + err =0 ;dout ("readdir %p file %p done.\n" , inode, file); -return 0 ; +out: +ceph_fname_free_buffer (inode, &tname); +ceph_fname_free_buffer (inode, &oname); +return err; }static void reset_readdir (struct ceph_dir_file_info *dfi)
fs/ceph/inode.c +35 -3
@@ -1722,7 +1722,8 @@ int ceph_readdir_prepopulate(struct ceph_mds_request *req, struct ceph_mds_session *session) {struct dentry *parent = req->r_dentry; -struct ceph_inode_info *ci =ceph_inode (d_inode (parent)); +struct inode *inode =d_inode (parent); +struct ceph_inode_info *ci =ceph_inode (inode);struct ceph_mds_reply_info_parsed *rinfo = &req->r_reply_info;struct qstr dname;struct dentry *dn;
@@ -1732,6 +1733,8 @@ int ceph_readdir_prepopulate(struct ceph_mds_request *req,u32 last_hash =0 ;u32 fpos_offset;struct ceph_readdir_cache_control cache_ctl = {}; +struct fscrypt_str tname =FSTR_INIT (NULL ,0 ); +struct fscrypt_str oname =FSTR_INIT (NULL ,0 );if (test_bit (CEPH_MDS_R_ABORTED , &req->r_req_flags))return readdir_prepopulate_inodes_only (req, session);
@@ -1783,14 +1786,36 @@ int ceph_readdir_prepopulate(struct ceph_mds_request *req, cache_ctl.index = req->r_readdir_cache_idx; fpos_offset = req->r_readdir_offset; + err =ceph_fname_alloc_buffer (inode, &tname); +if (err <0 ) + goto out; + + err =ceph_fname_alloc_buffer (inode, &oname); +if (err <0 ) + goto out; +/* FIXME: release caps/leases if error occurs */ for (i =0 ; i < rinfo->dir_nr; i++) { +bool is_nokey = false;struct ceph_mds_reply_dir_entry *rde = rinfo->dir_entries + i;struct ceph_vino tvino; +u32 olen = oname.len; +struct ceph_fname fname = { .dir = inode, + .name = rde->name, + .name_len = rde->name_len, + .ctext = rde->altname, + .ctext_len = rde->altname_len }; + + err =ceph_fname_to_usr (&fname, &tname, &oname, &is_nokey); +if (err) { +dout ("Unable to decode %.*s. Skipping it." , rde->name_len, rde->name); +continue ; + } - dname.name = rde->name; - dname.len = rde->name_len; + dname.name = oname.name; + dname.len = oname.len; dname.hash =full_name_hash (parent, dname.name, dname.len); + oname.len = olen; tvino.ino =le64_to_cpu (rde->inode.in->ino); tvino.snap =le64_to_cpu (rde->inode.in->snapid);
@@ -1821,6 +1846,11 @@ int ceph_readdir_prepopulate(struct ceph_mds_request *req, err = -ENOMEM ; goto out; } +if (is_nokey) { +spin_lock (&dn->d_lock); + dn->d_flags |=DCACHE_NOKEY_NAME ; +spin_unlock (&dn->d_lock); + } }else if (d_really_is_positive (dn) && (ceph_ino (d_inode (dn)) != tvino.ino ||ceph_snap (d_inode (dn)) != tvino.snap)) {
@@ -1911,6 +1941,8 @@ int ceph_readdir_prepopulate(struct ceph_mds_request *req, req->r_readdir_cache_idx = cache_ctl.index; }ceph_readdir_cache_release (&cache_ctl); +ceph_fname_free_buffer (inode, &tname); +ceph_fname_free_buffer (inode, &oname);dout ("readdir_prepopulate done\n" );return err; }
Signature · 1 line
2.30.2
RFC PATCH v6 18/20 ceph: create symlinks with encrypted and base64-encoded targets
In reply to Jeff LaytonWhen creating symlinks in encrypted directories, encrypt and base64-encode the target with the new inode's key before sending to the MDS.
When filling a symlinked inode, base64-decode it into a buffer that we'll keep in ci->i_symlink. When get_link is called, decrypt the buffer into a new one that will hang off i_link.
--- fs/ceph/dir.c | 52 ++++++++++++++++++++++++--- fs/ceph/inode.c | 95 ++++++++++++++++++++++++++++++++++++++++++------- 2 files changed, 130 insertions(+), 17 deletions(-)
fs/ceph/dir.c +47 -5
@@ -947,6 +947,40 @@ static int ceph_create(struct user_namespace *mnt_userns, struct inode *dir,return ceph_mknod (mnt_userns, dir, dentry, mode,0 ); } +#if IS_ENABLED (CONFIG_FS_ENCRYPTION ) +static int prep_encrypted_symlink_target (struct ceph_mds_request *req,const char *dest) +{ +int err; +int len =strlen (dest); +struct fscrypt_str osd_link =FSTR_INIT (NULL ,0 ); + + err =fscrypt_prepare_symlink (req->r_parent, dest, len,PATH_MAX , &osd_link); +if (err) + goto out; + + err =fscrypt_encrypt_symlink (req->r_new_inode, dest, len, &osd_link); +if (err) + goto out; + + req->r_path2 =kmalloc (FSCRYPT_BASE64_CHARS (osd_link.len) +1 ,GFP_KERNEL ); +if (!req->r_path2) { + err = -ENOMEM ; + goto out; + } + + len =fscrypt_base64_encode (osd_link.name, osd_link.len, req->r_path2); + req->r_path2[len] ='\0' ; +out: +fscrypt_fname_free_buffer (&osd_link); +return err; +} +#else +static int prep_encrypted_symlink_target (struct ceph_mds_request *req,const char *dest) +{ +return -EOPNOTSUPP ; +} +#endif +static int ceph_symlink (struct user_namespace *mnt_userns,struct inode *dir,struct dentry *dentry,const char *dest) {
@@ -978,12 +1012,20 @@ static int ceph_symlink(struct user_namespace *mnt_userns, struct inode *dir, goto out_req; } - req->r_path2 =kstrdup (dest,GFP_KERNEL ); -if (!req->r_path2) { - err = -ENOMEM ; - goto out_req; - } req->r_parent = dir; + +if (IS_ENCRYPTED (req->r_new_inode)) { + err =prep_encrypted_symlink_target (req, dest); +if (err) + goto out_req; + }else { + req->r_path2 =kstrdup (dest,GFP_KERNEL ); +if (!req->r_path2) { + err = -ENOMEM ; + goto out_req; + } + } +set_bit (CEPH_MDS_R_PARENT_LOCKED , &req->r_req_flags); req->r_dentry =dget (dentry); req->r_num_caps =2 ;
fs/ceph/inode.c +83 -12
146 lines not on this page · raw message
Signature · 1 line
2.30.2
RFC PATCH v6 19/20 ceph: make ceph_get_name decrypt filenames
In reply to Jeff LaytonWhen we do a lookupino to the MDS, we get a filename in the trace. ceph_get_name uses that name directly, so we must properly decrypt it before copying it to the name buffer.
--- fs/ceph/export.c | 42 +++++++++++++++++++++++++++++++----------- 1 file changed, 31 insertions(+), 11 deletions(-)
fs/ceph/export.c +31 -11
@@ -7,6 +7,7 @@#include "super.h" #include "mds_client.h" +#include "crypto.h" /* * Basic fh
@@ -524,7 +525,9 @@ static int ceph_get_name(struct dentry *parent, char *name, {struct ceph_mds_client *mdsc;struct ceph_mds_request *req; +struct inode *dir =d_inode (parent);struct inode *inode =d_inode (child); +struct ceph_mds_reply_info_parsed *rinfo;int err;if (ceph_snap (inode) !=CEPH_NOSNAP )
@@ -536,29 +539,46 @@ static int ceph_get_name(struct dentry *parent, char *name,if (IS_ERR (req))return PTR_ERR (req); -inode_lock (d_inode (parent)); - +inode_lock (dir); req->r_inode = inode;ihold (inode); req->r_ino2 =ceph_vino (d_inode (parent)); - req->r_parent =d_inode (parent); + req->r_parent = dir;set_bit (CEPH_MDS_R_PARENT_LOCKED , &req->r_req_flags); req->r_num_caps =2 ; err =ceph_mdsc_do_request (mdsc,NULL , req); +inode_unlock (dir); -inode_unlock (d_inode (parent)); +if (err) + goto out; -if (!err) { -struct ceph_mds_reply_info_parsed *rinfo = &req->r_reply_info; + rinfo = &req->r_reply_info; +if (!IS_ENCRYPTED (dir)) {memcpy (name, rinfo->dname, rinfo->dname_len); name[rinfo->dname_len] =0 ; -dout ("get_name %p ino %llx.%llx name %s\n" , - child,ceph_vinop (inode), name); }else { -dout ("get_name %p ino %llx.%llx err %d\n" , - child,ceph_vinop (inode), err); - } +struct fscrypt_str oname =FSTR_INIT (NULL ,0 ); +struct ceph_fname fname = { .dir = dir, + .name = rinfo->dname, + .ctext = rinfo->altname, + .name_len = rinfo->dname_len, + .ctext_len = rinfo->altname_len }; + + err =ceph_fname_alloc_buffer (dir, &oname); +if (err <0 ) + goto out; + err =ceph_fname_to_usr (&fname,NULL , &oname,NULL ); +if (!err) { +memcpy (name, oname.name, oname.len); + name[oname.len] =0 ; + } +ceph_fname_free_buffer (dir, &oname); + } +out: +dout ("get_name %p ino %llx.%llx err %d %s%s\n" , + child,ceph_vinop (inode), err, + err ?"" :"name " , err ?"" : name);ceph_mdsc_put_request (req);return err; }
Signature · 1 line
2.30.2
RFC PATCH v6 20/20 ceph: add fscrypt ioctls
In reply to Jeff LaytonWe gate most of the ioctls on 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.
For the set_policy ioctl, we take Fcx caps to ensure that nothing can create files in the directory while the ioctl is running. That should be enough to ensure that the "empty_dir" check is reliable.
--- fs/ceph/ioctl.c | 93 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 93 insertions(+)
fs/ceph/ioctl.c +93 -0
@@ -6,6 +6,7 @@#include "mds_client.h" #include "ioctl.h" #include <linux/ceph/striper.h> +#include <linux/fscrypt.h> /* * ioctls
@@ -268,8 +269,55 @@ 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 = mdsc->sessions[i]; + +if (!s) +continue ; +if (test_bit (CEPHFS_FEATURE_ALTERNATE_NAME , &s->s_features)) + ret =0 ; +break ; + } +mutex_unlock (&mdsc->mutex); +return ret; +} + +static long ceph_set_encryption_policy (struct file *file,unsigned long arg) +{ +int ret, got =0 ; +struct inode *inode =file_inode (file); +struct ceph_inode_info *ci =ceph_inode (inode); + + ret =vet_mds_for_fscrypt (file); +if (ret) +return ret; + +/* +* Ensure we hold these caps so that we _know_ that the rstats check +* in the empty_dir check is reliable. +*/ + ret =ceph_get_caps (file,CEPH_CAP_FILE_SHARED ,0 ,-1 , &got); +if (ret) +return ret; + + ret =fscrypt_ioctl_set_policy (file, (const void __user *)arg); +if (got) +ceph_put_cap_refs (ci, got); + +return ret; +} +long ceph_ioctl (struct file *file,unsigned int cmd,unsigned long arg) { +int ret; +struct ceph_inode_info *ci =ceph_inode (file_inode (file)); +dout ("ioctl file %p cmd %u arg %lu\n" , file, cmd, arg);switch (cmd) {case CEPH_IOC_GET_LAYOUT :
@@ -289,6 +337,51 @@ 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 : +return ceph_set_encryption_policy (file, 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; +atomic_inc (&ci->i_shared_gen); +ceph_dir_clear_ordered (file_inode (file)); +ceph_dir_clear_complete (file_inode (file)); +return fscrypt_ioctl_add_key (file, (void __user *)arg); + +case FS_IOC_REMOVE_ENCRYPTION_KEY : +atomic_inc (&ci->i_shared_gen); +ceph_dir_clear_ordered (file_inode (file)); +ceph_dir_clear_complete (file_inode (file)); +return fscrypt_ioctl_remove_key (file, (void __user *)arg); + +case FS_IOC_REMOVE_ENCRYPTION_KEY_ALL_USERS : +atomic_inc (&ci->i_shared_gen); +ceph_dir_clear_ordered (file_inode (file)); +ceph_dir_clear_complete (file_inode (file)); +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 ;
Signature · 1 line
2.30.2
Re: [RFC PATCH v6 20/20] ceph: add fscrypt ioctls
Hi Jeff!
Jeff Layton <[email protected]> writes:
<...>
fs/ceph/ioctl.c long ceph_ioctl(struct file *file, unsigned int cmd, unsigned long arg) · line 360
Quoted 6 lines
fs/ceph/ioctl.c +6
-0+ +case FS_IOC_ADD_ENCRYPTION_KEY : + ret =vet_mds_for_fscrypt (file); +if (ret) +return ret; +atomic_inc (&ci->i_shared_gen);
After spending some (well... a lot, actually) time looking at the MDS code to try to figure out my bug, I'm back at this point in the kernel client code. I understand that this code is trying to invalidate the directory dentries here. However, I just found that the directory we get at this point is the filesystem root directory, and not the directory we're trying to unlock.
So, I still don't fully understand the issue I'm seeing, but I believe the code above is assuming 'ci' is the inode being unlocked, which isn't correct.
(Note: I haven't checked if there are other ioctls getting the FS root.)
Cheers,
Signature · 1 line
Luis
Re: [RFC PATCH v6 20/20] ceph: add fscrypt ioctls
Quoted 18 lines · Luis Henriques
Hi Jeff!
Jeff Layton <[email protected]> writes:
<...>fs/ceph/ioctl.c long ceph_ioctl(struct file *file, unsigned int cmd, unsigned long arg) · line 360
Quoted 6 lines
fs/ceph/ioctl.c +6
-0+ +case FS_IOC_ADD_ENCRYPTION_KEY : + ret =vet_mds_for_fscrypt (file); +if (ret) +return ret; +atomic_inc (&ci->i_shared_gen);After spending some (well... a lot, actually) time looking at the MDS code to try to figure out my bug, I'm back at this point in the kernel client code. I understand that this code is trying to invalidate the directory dentries here. However, I just found that the directory we get at this point is the filesystem root directory, and not the directory we're trying to unlock.
Quoted 7 lines
So, I still don't fully understand the issue I'm seeing, but I believe the code above is assuming 'ci' is the inode being unlocked, which isn't correct.
(Note: I haven't checked if there are other ioctls getting the FS root.)
Cheers,
Oh, interesting. That was my assumption. I'll have to take a look more closely at what effect that might have then.
Thanks,
Signature · 1 line
Jeff Layton <[email protected]>
Eric Biggers
maintainerRe: [RFC PATCH v6 20/20] ceph: add fscrypt ioctls
Quoted 23 lines · Jeff Layton
Quoted 22 lines · Luis Henriques
Hi Jeff!
Jeff Layton <[email protected]> writes:
<...>fs/ceph/ioctl.c long ceph_ioctl(struct file *file, unsigned int cmd, unsigned long arg) · line 360
Quoted 6 lines
fs/ceph/ioctl.c +6
-0+ +case FS_IOC_ADD_ENCRYPTION_KEY : + ret =vet_mds_for_fscrypt (file); +if (ret) +return ret; +atomic_inc (&ci->i_shared_gen);After spending some (well... a lot, actually) time looking at the MDS code to try to figure out my bug, I'm back at this point in the kernel client code. I understand that this code is trying to invalidate the directory dentries here. However, I just found that the directory we get at this point is the filesystem root directory, and not the directory we're trying to unlock.
So, I still don't fully understand the issue I'm seeing, but I believe the code above is assuming 'ci' is the inode being unlocked, which isn't correct.
Quoted 8 lines
Quoted 3 lines
(Note: I haven't checked if there are other ioctls getting the FS root.)
Cheers,
Oh, interesting. That was my assumption. I'll have to take a look more closely at what effect that might have then.
FS_IOC_ADD_ENCRYPTION_KEY, FS_IOC_REMOVE_ENCRYPTION_KEY, FS_IOC_REMOVE_ENCRYPTION_KEY_ALL_USERS, and FS_IOC_GET_ENCRYPTION_KEY_STATUS can all be executed on any file or directory on the filesystem (but preferably on the root directory) because they are operations on the filesystem, not on any specific file or directory. They deal with encryption keys, which can protect any number of encrypted directories (even 0 or a large number) and/or even loose encrypted files that got moved into an unencrypted directory.
Note that this is all described in the documentation
(https://www.kernel.org/doc/html/latest/filesystems/fscrypt.html).
If the documentation is unclear please suggest improvements to it.
Also, there shouldn't be any need for FS_IOC_ADD_ENCRYPTION_KEY to invalidate dentries itself because that is the point of fscrypt_d_revalidate(); the invalidation happens on-demand later.
- Eric
Re: [RFC PATCH v6 20/20] ceph: add fscrypt ioctls
Quoted 41 lines · Eric Biggers
Quoted 23 lines · Jeff Layton
Quoted 22 lines · Luis Henriques
Hi Jeff!
Jeff Layton <[email protected]> writes:
<...>fs/ceph/ioctl.c long ceph_ioctl(struct file *file, unsigned int cmd, unsigned long arg) · line 360
Quoted 6 lines
fs/ceph/ioctl.c +6
-0+ +case FS_IOC_ADD_ENCRYPTION_KEY : + ret =vet_mds_for_fscrypt (file); +if (ret) +return ret; +atomic_inc (&ci->i_shared_gen);After spending some (well... a lot, actually) time looking at the MDS code to try to figure out my bug, I'm back at this point in the kernel client code. I understand that this code is trying to invalidate the directory dentries here. However, I just found that the directory we get at this point is the filesystem root directory, and not the directory we're trying to unlock.
So, I still don't fully understand the issue I'm seeing, but I believe the code above is assuming 'ci' is the inode being unlocked, which isn't correct.
Quoted 8 lines
Quoted 3 lines
(Note: I haven't checked if there are other ioctls getting the FS root.)
Cheers,
Oh, interesting. That was my assumption. I'll have to take a look more closely at what effect that might have then.
FS_IOC_ADD_ENCRYPTION_KEY,FS_IOC_REMOVE_ENCRYPTION_KEY,FS_IOC_REMOVE_ENCRYPTION_KEY_ALL_USERS, andFS_IOC_GET_ENCRYPTION_KEY_STATUScan all be executed on any file or directory on the filesystem (but preferably on the root directory) because they are operations on the filesystem, not on any specific file or directory. They deal with encryption keys, which can protect any number of encrypted directories (even 0 or a large number) and/or even loose encrypted files that got moved into an unencrypted directory.
Quoted 7 lines
Note that this is all described in the documentation
(https://www.kernel.org/doc/html/latest/filesystems/fscrypt.html).
If the documentation is unclear please suggest improvements to it.Also, there shouldn't be any need for
FS_IOC_ADD_ENCRYPTION_KEYto invalidate dentries itself because that is the point offscrypt_d_revalidate(); the invalidation happens on-demand later.
I think the documentation is very clear regarding these ioctls. I guess I just need to go refresh my memory as I have read that document long time ago. Thanks for reminding me to do that ;-)
Cheers,
Signature · 1 line
Luis
Re: [RFC PATCH v6 20/20] ceph: add fscrypt ioctls
In reply to Eric BiggersQuoted 41 lines · Eric Biggers
Quoted 23 lines · Jeff Layton
Quoted 22 lines · Luis Henriques
Hi Jeff!
Jeff Layton <[email protected]> writes:
<...>fs/ceph/ioctl.c long ceph_ioctl(struct file *file, unsigned int cmd, unsigned long arg) · line 360
Quoted 6 lines
fs/ceph/ioctl.c +6
-0+ +case FS_IOC_ADD_ENCRYPTION_KEY : + ret =vet_mds_for_fscrypt (file); +if (ret) +return ret; +atomic_inc (&ci->i_shared_gen);After spending some (well... a lot, actually) time looking at the MDS code to try to figure out my bug, I'm back at this point in the kernel client code. I understand that this code is trying to invalidate the directory dentries here. However, I just found that the directory we get at this point is the filesystem root directory, and not the directory we're trying to unlock.
So, I still don't fully understand the issue I'm seeing, but I believe the code above is assuming 'ci' is the inode being unlocked, which isn't correct.
Quoted 8 lines
Quoted 3 lines
(Note: I haven't checked if there are other ioctls getting the FS root.)
Cheers,
Oh, interesting. That was my assumption. I'll have to take a look more closely at what effect that might have then.
FS_IOC_ADD_ENCRYPTION_KEY,FS_IOC_REMOVE_ENCRYPTION_KEY,FS_IOC_REMOVE_ENCRYPTION_KEY_ALL_USERS, andFS_IOC_GET_ENCRYPTION_KEY_STATUScan all be executed on any file or directory on the filesystem (but preferably on the root directory) because they are operations on the filesystem, not on any specific file or directory. They deal with encryption keys, which can protect any number of encrypted directories (even 0 or a large number) and/or even loose encrypted files that got moved into an unencrypted directory.
Quoted 7 lines
Note that this is all described in the documentation
(https://www.kernel.org/doc/html/latest/filesystems/fscrypt.html).
If the documentation is unclear please suggest improvements to it.Also, there shouldn't be any need for
FS_IOC_ADD_ENCRYPTION_KEYto invalidate dentries itself because that is the point offscrypt_d_revalidate(); the invalidation happens on-demand later.
Ok, thanks. I'll plan to drop the invalidation from the ioctl codepaths, and leave it up to fscrypt_d_revalidate to sort out.
Signature · 1 line
Jeff Layton <[email protected]>
Quoted 8 lines · Jeff Layton
The main change in this posting is in the detection of fscrypted inodes. The older set would grovel around in the xattr blob to see if it had an "encryption.ctx" xattr. This was problematic if the MDS didn't send xattrs in the trace, and not very efficient.
This posting changes it to use the new "fscrypt" flag, which should always be reported by the MDS (Luis, I'm hoping this may fix the issues you were seeing with dcache coherency).
I just fetched from your updated 'ceph-fscrypt-fnames' branch (which I assume contains this RFC series) and I'm now seeing the splat bellow.
Cheers,
--
Luis
[ 149.508364] ============================================
[ 149.511075] WARNING: possible recursive locking detected
[ 149.513652] 5.12.0-rc4+ #140 Not tainted
[ 149.515656] --------------------------------------------
[ 149.518293] cat/273 is trying to acquire lock:
[ 149.520570] ffff88813b3f6070 (&mdsc->mutex){+.+.}-{3:3}, at: ceph_mdsc_submit_request+0x206/0x600 [ceph]
[ 149.525497]
[ 149.525497] but task is already holding lock:
[ 149.528420] ffff88813b3f6070 (&mdsc->mutex){+.+.}-{3:3}, at: ceph_mdsc_submit_request+0x206/0x600 [ceph]
[ 149.533163]
[ 149.533163] other info that might help us debug this:
[ 149.536383] Possible unsafe locking scenario:
[ 149.536383]
[ 149.539344] CPU0
[ 149.540588] ----
[ 149.541870] lock(&mdsc->mutex);
[ 149.543534] lock(&mdsc->mutex);
[ 149.545205]
[ 149.545205] *** DEADLOCK ***
[ 149.545205]
[ 149.548142] May be due to missing lock nesting notation
[ 149.548142]
[ 149.551254] 2 locks held by cat/273:
[ 149.552926] #0: ffff88812296b590 (&type->i_mutex_dir_key#7){++++}-{3:3}, at: path_openat+0x959/0xe10
[ 149.556923] #1: ffff88813b3f6070 (&mdsc->mutex){+.+.}-{3:3}, at: ceph_mdsc_submit_request+0x206/0x600 [ceph]
[ 149.560954]
[ 149.560954] stack backtrace:
[ 149.562574] CPU: 0 PID: 273 Comm: cat Not tainted 5.12.0-rc4+ #140
[ 149.564785] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014
[ 149.567573] Call Trace:
[ 149.568207] dump_stack+0x93/0xc2
[ 149.569072] __lock_acquire.cold+0x2e5/0x30f
[ 149.570100] ? lockdep_hardirqs_on_prepare+0x1f0/0x1f0
[ 149.571318] ? stack_trace_save+0x91/0xc0
[ 149.572272] ? mark_held_locks+0x65/0x90
[ 149.573196] lock_acquire+0x16d/0x4e0
[ 149.574030] ? ceph_mdsc_submit_request+0x206/0x600 [ceph]
[ 149.575340] ? lock_release+0x410/0x410
[ 149.576211] ? lockdep_hardirqs_on_prepare+0x1f0/0x1f0
[ 149.577348] ? mark_lock+0x101/0x1a20
[ 149.578145] ? mark_lock+0x101/0x1a20
[ 149.578948] __mutex_lock+0xfd/0xb80
[ 149.579773] ? ceph_mdsc_submit_request+0x206/0x600 [ceph]
[ 149.581031] ? ceph_mdsc_submit_request+0x206/0x600 [ceph]
[ 149.582174] ? ceph_get_cap_refs+0x1c/0x40 [ceph]
[ 149.583171] ? mutex_lock_io_nested+0xab0/0xab0
[ 149.584079] ? lock_release+0x1ea/0x410
[ 149.584869] ? ceph_mdsc_submit_request+0x42/0x600 [ceph]
[ 149.585962] ? lock_downgrade+0x390/0x390
[ 149.586737] ? lock_is_held_type+0x98/0x110
[ 149.587565] ? ceph_take_cap_refs+0x43/0x220 [ceph]
[ 149.588560] ceph_mdsc_submit_request+0x206/0x600 [ceph]
[ 149.589603] ceph_mdsc_do_request+0x31/0x320 [ceph]
[ 149.590554] __ceph_do_getattr+0xf9/0x2b0 [ceph]
[ 149.591453] __ceph_getxattr+0x2fa/0x480 [ceph]
[ 149.592337] ? find_held_lock+0x85/0xa0
[ 149.593055] ? lock_is_held_type+0x98/0x110
[ 149.593799] ceph_crypt_get_context+0x17/0x20 [ceph]
[ 149.594732] fscrypt_get_encryption_info+0x133/0x220
[ 149.595621] ? fscrypt_prepare_new_inode+0x160/0x160
[ 149.596512] ? dget_parent+0x95/0x2f0
[ 149.597166] ? lock_downgrade+0x390/0x390
[ 149.597850] ? rwlock_bug.part.0+0x60/0x60
[ 149.598567] ? lock_downgrade+0x390/0x390
[ 149.599251] ? do_raw_spin_unlock+0x93/0xf0
[ 149.599968] ? dget_parent+0xc4/0x2f0
[ 149.600604] ceph_mdsc_build_path.part.0+0x367/0x7c0 [ceph]
[ 149.601587] ? remove_session_caps_cb+0x7b0/0x7b0 [ceph]
[ 149.602506] ? __lock_acquire+0x863/0x3070
[ 149.603188] ? lockdep_hardirqs_on_prepare+0x1f0/0x1f0
[ 149.604030] ? __is_insn_slot_addr+0xc9/0x140
[ 149.604774] ? mark_lock+0x101/0x1a20
[ 149.605365] ? lock_is_held_type+0x98/0x110
[ 149.606040] ? find_held_lock+0x85/0xa0
[ 149.606660] ? lock_release+0x1ea/0x410
[ 149.607279] ? set_request_path_attr+0x173/0x500 [ceph]
[ 149.608174] ? lock_downgrade+0x390/0x390
[ 149.608825] ? find_held_lock+0x85/0xa0
[ 149.609443] ? lockdep_hardirqs_on_prepare+0x1f0/0x1f0
[ 149.610267] ? lock_release+0x1ea/0x410
[ 149.610924] set_request_path_attr+0x1a5/0x500 [ceph]
[ 149.611811] __prepare_send_request+0x30e/0x13c0 [ceph]
[ 149.612847] ? rwlock_bug.part.0+0x60/0x60
[ 149.613551] ? set_request_path_attr+0x500/0x500 [ceph]
[ 149.614540] ? __choose_mds+0x323/0xcb0 [ceph]
[ 149.615398] ? trim_caps_cb+0x3b0/0x3b0 [ceph]
[ 149.616215] ? rwlock_bug.part.0+0x60/0x60
[ 149.616953] ? ceph_get_mds_session+0xad/0x1e0 [ceph]
[ 149.617847] ? ceph_session_state_name+0x30/0x30 [ceph]
[ 149.618788] ? ceph_reserve_caps+0x331/0x5a0 [ceph]
[ 149.619626] __do_request+0x338/0x9b0 [ceph]
[ 149.620376] ? cleanup_session_requests+0x1b0/0x1b0 [ceph]
[ 149.621347] ? lock_is_held_type+0x98/0x110
[ 149.622052] ceph_mdsc_submit_request+0x4af/0x600 [ceph]
[ 149.622998] ceph_mdsc_do_request+0x31/0x320 [ceph]
[ 149.623885] ceph_atomic_open+0x3be/0x1050 [ceph]
[ 149.624729] ? d_alloc_parallel+0x576/0xe50
[ 149.625309] ? ceph_renew_caps+0x270/0x270 [ceph]
[ 149.625986] ? __d_lookup_rcu+0x2e0/0x2e0
[ 149.626539] ? lock_is_held_type+0x98/0x110
[ 149.627113] ? lockdep_hardirqs_on_prepare+0x12e/0x1f0
[ 149.627835] lookup_open.isra.0+0x5d2/0x7f0
[ 149.628407] ? hashlen_string+0xa0/0xa0
[ 149.628961] path_openat+0x457/0xe10
[ 149.629468] ? path_parentat+0xc0/0xc0
[ 149.630047] ? __alloc_pages_slowpath.constprop.0+0x1070/0x1070
[ 149.630825] ? lockdep_hardirqs_on_prepare+0x1f0/0x1f0
[ 149.631540] ? mntput_no_expire+0xe6/0x650
[ 149.632080] ? mark_held_locks+0x24/0x90
[ 149.632605] do_filp_open+0x10b/0x220
[ 149.633100] ? may_open_dev+0x50/0x50
[ 149.633577] ? lock_downgrade+0x390/0x390
[ 149.634147] ? do_raw_spin_lock+0x119/0x1b0
[ 149.634785] ? rwlock_bug.part.0+0x60/0x60
[ 149.635423] ? do_raw_spin_unlock+0x93/0xf0
[ 149.636094] ? _raw_spin_unlock+0x1f/0x30
[ 149.636735] ? alloc_fd+0x150/0x300
[ 149.637284] do_sys_openat2+0x115/0x240
[ 149.637887] ? build_open_flags+0x270/0x270
[ 149.638511] ? __ia32_compat_sys_newlstat+0x30/0x30
[ 149.639264] __x64_sys_openat+0xce/0x140
[ 149.639878] ? __ia32_compat_sys_open+0x120/0x120
[ 149.640622] ? lockdep_hardirqs_on_prepare+0x12e/0x1f0
[ 149.641389] ? syscall_enter_from_user_mode+0x1d/0x50
[ 149.642175] ? trace_hardirqs_on+0x32/0x100
[ 149.642835] do_syscall_64+0x33/0x40
[ 149.643395] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 149.644165] RIP: 0033:0x7f6d190daffb
[ 149.644705] Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00 00 00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 5
[ 149.647306] RSP: 002b:00007ffe706cec20 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
[ 149.648294] RAX: ffffffffffffffda RBX: 000055656fd16000 RCX: 00007f6d190daffb
[ 149.649200] RDX: 0000000000000000 RSI: 00007ffe706d0eda RDI: 00000000ffffff9c
[ 149.650094] RBP: 00007ffe706d0eda R08: 0000000000000000 R09: 0000000000000000
[ 149.650983] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
[ 149.651876] R13: 0000000000000002 R14: 00007ffe706cef48 R15: 0000000000020000Quoted 145 lines · Luis Henriques
Quoted 8 lines · Jeff Layton
The main change in this posting is in the detection of fscrypted inodes. The older set would grovel around in the xattr blob to see if it had an "encryption.ctx" xattr. This was problematic if the MDS didn't send xattrs in the trace, and not very efficient.
This posting changes it to use the new "fscrypt" flag, which should always be reported by the MDS (Luis, I'm hoping this may fix the issues you were seeing with dcache coherency).
I just fetched from your updated 'ceph-fscrypt-fnames' branch (which I assume contains this RFC series) and I'm now seeing the splat bellow.
Cheers,
--
Luis[ 149.508364] ============================================ [ 149.511075] WARNING: possible recursive locking detected [ 149.513652] 5.12.0-rc4+ #140 Not tainted [ 149.515656] -------------------------------------------- [ 149.518293] cat/273 is trying to acquire lock: [ 149.520570] ffff88813b3f6070 (&mdsc->mutex){+.+.}-{3:3}, at: ceph_mdsc_submit_request+0x206/0x600 [ceph] [ 149.525497] [ 149.525497] but task is already holding lock: [ 149.528420] ffff88813b3f6070 (&mdsc->mutex){+.+.}-{3:3}, at: ceph_mdsc_submit_request+0x206/0x600 [ceph] [ 149.533163] [ 149.533163] other info that might help us debug this: [ 149.536383] Possible unsafe locking scenario: [ 149.536383] [ 149.539344] CPU0 [ 149.540588] ---- [ 149.541870] lock(&mdsc->mutex); [ 149.543534] lock(&mdsc->mutex); [ 149.545205] [ 149.545205] *** DEADLOCK *** [ 149.545205] [ 149.548142] May be due to missing lock nesting notation [ 149.548142] [ 149.551254] 2 locks held by cat/273: [ 149.552926] #0: ffff88812296b590 (&type->i_mutex_dir_key#7){++++}-{3:3}, at: path_openat+0x959/0xe10 [ 149.556923] #1: ffff88813b3f6070 (&mdsc->mutex){+.+.}-{3:3}, at: ceph_mdsc_submit_request+0x206/0x600 [ceph] [ 149.560954] [ 149.560954] stack backtrace: [ 149.562574] CPU: 0 PID: 273 Comm: cat Not tainted 5.12.0-rc4+ #140 [ 149.564785] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014 [ 149.567573] Call Trace: [ 149.568207] dump_stack+0x93/0xc2 [ 149.569072] __lock_acquire.cold+0x2e5/0x30f [ 149.570100] ? lockdep_hardirqs_on_prepare+0x1f0/0x1f0 [ 149.571318] ? stack_trace_save+0x91/0xc0 [ 149.572272] ? mark_held_locks+0x65/0x90 [ 149.573196] lock_acquire+0x16d/0x4e0 [ 149.574030] ? ceph_mdsc_submit_request+0x206/0x600 [ceph] [ 149.575340] ? lock_release+0x410/0x410 [ 149.576211] ? lockdep_hardirqs_on_prepare+0x1f0/0x1f0 [ 149.577348] ? mark_lock+0x101/0x1a20 [ 149.578145] ? mark_lock+0x101/0x1a20 [ 149.578948] __mutex_lock+0xfd/0xb80 [ 149.579773] ? ceph_mdsc_submit_request+0x206/0x600 [ceph] [ 149.581031] ? ceph_mdsc_submit_request+0x206/0x600 [ceph] [ 149.582174] ? ceph_get_cap_refs+0x1c/0x40 [ceph] [ 149.583171] ? mutex_lock_io_nested+0xab0/0xab0 [ 149.584079] ? lock_release+0x1ea/0x410 [ 149.584869] ? ceph_mdsc_submit_request+0x42/0x600 [ceph] [ 149.585962] ? lock_downgrade+0x390/0x390 [ 149.586737] ? lock_is_held_type+0x98/0x110 [ 149.587565] ? ceph_take_cap_refs+0x43/0x220 [ceph] [ 149.588560] ceph_mdsc_submit_request+0x206/0x600 [ceph] [ 149.589603] ceph_mdsc_do_request+0x31/0x320 [ceph] [ 149.590554] __ceph_do_getattr+0xf9/0x2b0 [ceph] [ 149.591453] __ceph_getxattr+0x2fa/0x480 [ceph] [ 149.592337] ? find_held_lock+0x85/0xa0 [ 149.593055] ? lock_is_held_type+0x98/0x110 [ 149.593799] ceph_crypt_get_context+0x17/0x20 [ceph] [ 149.594732] fscrypt_get_encryption_info+0x133/0x220 [ 149.595621] ? fscrypt_prepare_new_inode+0x160/0x160 [ 149.596512] ? dget_parent+0x95/0x2f0 [ 149.597166] ? lock_downgrade+0x390/0x390 [ 149.597850] ? rwlock_bug.part.0+0x60/0x60 [ 149.598567] ? lock_downgrade+0x390/0x390 [ 149.599251] ? do_raw_spin_unlock+0x93/0xf0 [ 149.599968] ? dget_parent+0xc4/0x2f0 [ 149.600604] ceph_mdsc_build_path.part.0+0x367/0x7c0 [ceph] [ 149.601587] ? remove_session_caps_cb+0x7b0/0x7b0 [ceph] [ 149.602506] ? __lock_acquire+0x863/0x3070 [ 149.603188] ? lockdep_hardirqs_on_prepare+0x1f0/0x1f0 [ 149.604030] ? __is_insn_slot_addr+0xc9/0x140 [ 149.604774] ? mark_lock+0x101/0x1a20 [ 149.605365] ? lock_is_held_type+0x98/0x110 [ 149.606040] ? find_held_lock+0x85/0xa0 [ 149.606660] ? lock_release+0x1ea/0x410 [ 149.607279] ? set_request_path_attr+0x173/0x500 [ceph] [ 149.608174] ? lock_downgrade+0x390/0x390 [ 149.608825] ? find_held_lock+0x85/0xa0 [ 149.609443] ? lockdep_hardirqs_on_prepare+0x1f0/0x1f0 [ 149.610267] ? lock_release+0x1ea/0x410 [ 149.610924] set_request_path_attr+0x1a5/0x500 [ceph] [ 149.611811] __prepare_send_request+0x30e/0x13c0 [ceph] [ 149.612847] ? rwlock_bug.part.0+0x60/0x60 [ 149.613551] ? set_request_path_attr+0x500/0x500 [ceph] [ 149.614540] ? __choose_mds+0x323/0xcb0 [ceph] [ 149.615398] ? trim_caps_cb+0x3b0/0x3b0 [ceph] [ 149.616215] ? rwlock_bug.part.0+0x60/0x60 [ 149.616953] ? ceph_get_mds_session+0xad/0x1e0 [ceph] [ 149.617847] ? ceph_session_state_name+0x30/0x30 [ceph] [ 149.618788] ? ceph_reserve_caps+0x331/0x5a0 [ceph] [ 149.619626] __do_request+0x338/0x9b0 [ceph] [ 149.620376] ? cleanup_session_requests+0x1b0/0x1b0 [ceph] [ 149.621347] ? lock_is_held_type+0x98/0x110 [ 149.622052] ceph_mdsc_submit_request+0x4af/0x600 [ceph] [ 149.622998] ceph_mdsc_do_request+0x31/0x320 [ceph] [ 149.623885] ceph_atomic_open+0x3be/0x1050 [ceph] [ 149.624729] ? d_alloc_parallel+0x576/0xe50 [ 149.625309] ? ceph_renew_caps+0x270/0x270 [ceph] [ 149.625986] ? __d_lookup_rcu+0x2e0/0x2e0 [ 149.626539] ? lock_is_held_type+0x98/0x110 [ 149.627113] ? lockdep_hardirqs_on_prepare+0x12e/0x1f0 [ 149.627835] lookup_open.isra.0+0x5d2/0x7f0 [ 149.628407] ? hashlen_string+0xa0/0xa0 [ 149.628961] path_openat+0x457/0xe10 [ 149.629468] ? path_parentat+0xc0/0xc0 [ 149.630047] ? __alloc_pages_slowpath.constprop.0+0x1070/0x1070 [ 149.630825] ? lockdep_hardirqs_on_prepare+0x1f0/0x1f0 [ 149.631540] ? mntput_no_expire+0xe6/0x650 [ 149.632080] ? mark_held_locks+0x24/0x90 [ 149.632605] do_filp_open+0x10b/0x220 [ 149.633100] ? may_open_dev+0x50/0x50 [ 149.633577] ? lock_downgrade+0x390/0x390 [ 149.634147] ? do_raw_spin_lock+0x119/0x1b0 [ 149.634785] ? rwlock_bug.part.0+0x60/0x60 [ 149.635423] ? do_raw_spin_unlock+0x93/0xf0 [ 149.636094] ? _raw_spin_unlock+0x1f/0x30 [ 149.636735] ? alloc_fd+0x150/0x300 [ 149.637284] do_sys_openat2+0x115/0x240 [ 149.637887] ? build_open_flags+0x270/0x270 [ 149.638511] ? __ia32_compat_sys_newlstat+0x30/0x30 [ 149.639264] __x64_sys_openat+0xce/0x140 [ 149.639878] ? __ia32_compat_sys_open+0x120/0x120 [ 149.640622] ? lockdep_hardirqs_on_prepare+0x12e/0x1f0 [ 149.641389] ? syscall_enter_from_user_mode+0x1d/0x50 [ 149.642175] ? trace_hardirqs_on+0x32/0x100 [ 149.642835] do_syscall_64+0x33/0x40 [ 149.643395] entry_SYSCALL_64_after_hwframe+0x44/0xae
Quoted 8 lines
[ 149.644165] RIP: 0033:0x7f6d190daffb [ 149.644705] Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00 00 00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 5 [ 149.647306] RSP: 002b:00007ffe706cec20 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 [ 149.648294] RAX: ffffffffffffffda RBX: 000055656fd16000 RCX: 00007f6d190daffb [ 149.649200] RDX: 0000000000000000 RSI: 00007ffe706d0eda RDI: 00000000ffffff9c [ 149.650094] RBP: 00007ffe706d0eda R08: 0000000000000000 R09: 0000000000000000 [ 149.650983] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 [ 149.651876] R13: 0000000000000002 R14: 00007ffe706cef48 R15: 0000000000020000
Ouch. That looks like a real bug, alright.
Basically when building the path, we occasionally need to fetch the crypto context for parent inodes and such, and that can cause us to recurse back into __ceph_getxattr and try to issue another RPC to the MDS.
I'll have to look and see what we can do. Maybe it's safe to drop the mdsc->mutex while we're building the path? Or maybe this is a good time to re-think a lot of the really onerous locking in this codepath?
I'm open to suggestions here...
Signature · 1 line
Jeff Layton <[email protected]>
Quoted 1 line · Jeff Layton
On Mon, 2021-04-19 at 11:30 +0100, Luis Henriques wrote:
...
Quoted 7 lines
Ouch. That looks like a real bug, alright.
Basically when building the path, we occasionally need to fetch the crypto context for parent inodes and such, and that can cause us to recurse back into
__ceph_getxattrand try to issue another RPC to the MDS.
Quoted 5 lines
I'll have to look and see what we can do. Maybe it's safe to drop the
mdsc->mutexwhile we're building the path? Or maybe this is a good time to re-think a lot of the really onerous locking in this codepath?I'm open to suggestions here...
Yeah, I couldn't see a good fix at a first glace. Dropping the mutex while building the path was my initial thought too but it's not easy to proof that's a safe thing to do.
The other idea I had was to fetch all the needed fscrypt contexts at the end, after building the path. But I didn't found a way for doing that because to build the path... we need the contexts.
It looks like this leaves us with the locking rethinking option.
/me tries harder to find another way out
Cheers,
Signature · 1 line
Luis
Quoted 15 lines · Luis Henriques
Quoted 1 line · Jeff Layton
On Mon, 2021-04-19 at 11:30 +0100, Luis Henriques wrote:
...
Quoted 11 lines
Ouch. That looks like a real bug, alright.
Basically when building the path, we occasionally need to fetch the crypto context for parent inodes and such, and that can cause us to recurse back into
__ceph_getxattrand try to issue another RPC to the MDS.I'll have to look and see what we can do. Maybe it's safe to drop the
mdsc->mutexwhile we're building the path? Or maybe this is a good time to re-think a lot of the really onerous locking in this codepath?
Quoted 6 lines
Quoted 1 line
I'm open to suggestions here...
Yeah, I couldn't see a good fix at a first glace. Dropping the mutex while building the path was my initial thought too but it's not easy to proof that's a safe thing to do.
Indeed. It's an extremely coarse-grained mutex and not at all clear what it protects here.
Quoted 9 lines
The other idea I had was to fetch all the needed fscrypt contexts at the end, after building the path. But I didn't found a way for doing that because to build the path... we need the contexts.
It looks like this leaves us with the locking rethinking option.
/me tries harder to find another way out
Cheers,
The other option I think is to not store the context in an xattr at all, and instead make a dedicated field in the inode for it that we can ensure is always present for encrypted inodes. For the most part the crypto context is a static thing. The only exception is when we're first encrypting an empty dir.
We already have the fscrypt bool in the inodestat, and we're going to need another field to hold the real size for files. It may be worthwhile to just reconsider the design at that level. Maybe we just need to carve out a chunk of fscrypt space in the inode for the client and let it manage that however it sees fit.
Signature · 1 line
Jeff Layton <[email protected]>
Quoted 42 lines · Jeff Layton
Quoted 15 lines · Luis Henriques
Quoted 1 line · Jeff Layton
On Mon, 2021-04-19 at 11:30 +0100, Luis Henriques wrote:
...
Quoted 11 lines
Ouch. That looks like a real bug, alright.
Basically when building the path, we occasionally need to fetch the crypto context for parent inodes and such, and that can cause us to recurse back into
__ceph_getxattrand try to issue another RPC to the MDS.I'll have to look and see what we can do. Maybe it's safe to drop the
mdsc->mutexwhile we're building the path? Or maybe this is a good time to re-think a lot of the really onerous locking in this codepath?Quoted 6 lines
Quoted 1 line
I'm open to suggestions here...
Yeah, I couldn't see a good fix at a first glace. Dropping the mutex while building the path was my initial thought too but it's not easy to proof that's a safe thing to do.
Indeed. It's an extremely coarse-grained mutex and not at all clear what it protects here.
Quoted 9 lines
The other idea I had was to fetch all the needed fscrypt contexts at the end, after building the path. But I didn't found a way for doing that because to build the path... we need the contexts.
It looks like this leaves us with the locking rethinking option.
/me tries harder to find another way out
Cheers,
The other option I think is to not store the context in an xattr at all, and instead make a dedicated field in the inode for it that we can ensure is always present for encrypted inodes. For the most part the crypto context is a static thing. The only exception is when we're first encrypting an empty dir.
Quoted 5 lines
We already have the fscrypt bool in the inodestat, and we're going to need another field to hold the real size for files. It may be worthwhile to just reconsider the design at that level. Maybe we just need to carve out a chunk of fscrypt space in the inode for the client and let it manage that however it sees fit.
That's another solution. Since the initial (naïfe) idea of having a client-only implementation with fscrypt-agnostic MDSs is long gone, the design can (still) be fixed to do that. This will definitely allow to move forward with the fscrypt implementation. (But we'll probably be bitten again with these recursive RPCs in the future!)
Anyway, this is probably the most interesting solution as it also reduces the need for extra calls to MDS. And the fscrypt bool in inodestat probably becomes redundant and can be dropped.
Cheers,
Signature · 1 line
Luis
Quoted 56 lines · Luis Henriques
Quoted 42 lines · Jeff Layton
Quoted 15 lines · Luis Henriques
Quoted 1 line · Jeff Layton
On Mon, 2021-04-19 at 11:30 +0100, Luis Henriques wrote:
...
Quoted 11 lines
Ouch. That looks like a real bug, alright.
Basically when building the path, we occasionally need to fetch the crypto context for parent inodes and such, and that can cause us to recurse back into
__ceph_getxattrand try to issue another RPC to the MDS.I'll have to look and see what we can do. Maybe it's safe to drop the
mdsc->mutexwhile we're building the path? Or maybe this is a good time to re-think a lot of the really onerous locking in this codepath?Quoted 6 lines
Quoted 1 line
I'm open to suggestions here...
Yeah, I couldn't see a good fix at a first glace. Dropping the mutex while building the path was my initial thought too but it's not easy to proof that's a safe thing to do.
Indeed. It's an extremely coarse-grained mutex and not at all clear what it protects here.
Quoted 9 lines
The other idea I had was to fetch all the needed fscrypt contexts at the end, after building the path. But I didn't found a way for doing that because to build the path... we need the contexts.
It looks like this leaves us with the locking rethinking option.
/me tries harder to find another way out
Cheers,
The other option I think is to not store the context in an xattr at all, and instead make a dedicated field in the inode for it that we can ensure is always present for encrypted inodes. For the most part the crypto context is a static thing. The only exception is when we're first encrypting an empty dir.
Quoted 5 lines
We already have the fscrypt bool in the inodestat, and we're going to need another field to hold the real size for files. It may be worthwhile to just reconsider the design at that level. Maybe we just need to carve out a chunk of fscrypt space in the inode for the client and let it manage that however it sees fit.
That's another solution. Since the initial (naïfe) idea of having a client-only implementation with fscrypt-agnostic MDSs is long gone, the design can (still) be fixed to do that. This will definitely allow to move forward with the fscrypt implementation. (But we'll probably be bitten again with these recursive RPCs in the future!)
Quoted 4 lines
Anyway, this is probably the most interesting solution as it also reduces the need for extra calls to MDS. And the fscrypt bool in inodestat probably becomes redundant and can be dropped.
We probably can't drop the bool from the protocol, as it's now in a released version (Pacific).
What we can do is drop tracking the bool internally in the MDS, and just set that to true if the fscrypt blob isn't zero-length.
Cheers,
Signature · 1 line
Jeff Layton <[email protected]>