diff options
| author | Eric Biggers <ebiggers@google.com> | 2021-09-09 11:45:13 -0700 |
|---|---|---|
| committer | Eric Biggers <ebiggers@google.com> | 2021-09-20 19:32:33 -0700 |
| commit | 4373b3dc922038e8924f648506f6556f2afa7e77 (patch) | |
| tree | 315ddf83133cc6b0bacd418a349710fef86bf089 /include/linux/fscrypt.h | |
| parent | e4e737bb5c170df6135a127739a9e6148ee3da82 (diff) | |
fscrypt: remove fscrypt_operations::max_namelen
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.
Link: https://lore.kernel.org/r/20210909184513.139281-1-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@google.com>
Diffstat (limited to 'include/linux/fscrypt.h')
| -rw-r--r-- | include/linux/fscrypt.h | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/include/linux/fscrypt.h b/include/linux/fscrypt.h index e912ed9141d9..91ea9477e9bd 100644 --- a/include/linux/fscrypt.h +++ b/include/linux/fscrypt.h @@ -118,9 +118,6 @@ struct fscrypt_operations { */ bool (*empty_dir)(struct inode *inode); - /* The filesystem's maximum ciphertext filename length, in bytes */ - unsigned int max_namelen; - /* * Check whether the filesystem's inode numbers and UUID are stable, * meaning that they will never be changed even by offline operations |