[PATCH] fscrypt: remove fscrypt_operations::max_namelen
Eric Biggers
ebiggers at kernel.org
Mon Sep 20 20:17:42 PDT 2021
On Thu, Sep 09, 2021 at 11:45:13AM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers at google.com>
>
> The max_namelen field is unnecessary, as it is set to 255 (NAME_MAX) on
> all filesystems that support fscrypt (or plan to support fscrypt). For
> simplicity, just use NAME_MAX directly instead.
>
> Signed-off-by: Eric Biggers <ebiggers at google.com>
> ---
> fs/crypto/fname.c | 3 +--
> fs/ext4/super.c | 1 -
> fs/f2fs/super.c | 1 -
> fs/ubifs/crypto.c | 1 -
> include/linux/fscrypt.h | 3 ---
> 5 files changed, 1 insertion(+), 8 deletions(-)
Applied to fscrypt.git#master for 5.16.
- Eric
More information about the linux-mtd
mailing list