diff options
author | Jeff Layton <jlayton@kernel.org> | 2021-01-08 23:34:38 +0300 |
---|---|---|
committer | Ilya Dryomov <idryomov@gmail.com> | 2022-08-03 01:54:11 +0300 |
commit | d3e94fdc4ef476ca1edd468cc11badf2dbbb3c00 (patch) | |
tree | a546f8826c77eb4a0ae6a26577aa8aa1883b9843 /README | |
parent | 18cc912b8a2acaf32589241fbac47192ab90db14 (diff) | |
download | linux-d3e94fdc4ef476ca1edd468cc11badf2dbbb3c00.tar.xz |
fscrypt: export fscrypt_fname_encrypt and fscrypt_fname_encrypted_size
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@kernel.org>
Reviewed-by: Xiubo Li <xiubli@redhat.com>
Acked-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions