On Tue, Jan 11, 2022 at 02:15:23PM -0500, Jeff Layton wrote: > For 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. > > Signed-off-by: Jeff Layton <jlayton@xxxxxxxxxx> Acked-by: Eric Biggers <ebiggers@xxxxxxxxxx> Please make sure to run checkpatch.pl, though. There is still some weird indentation in this patch. - Eric
|