diff options
| author | Eric Biggers <ebiggers@google.com> | 2023-09-25 07:54:50 +0200 |
|---|---|---|
| committer | Eric Biggers <ebiggers@google.com> | 2023-09-26 07:34:33 +0200 |
| commit | 7a0263dc904f3467f474e4088ae092eda9a5a99b (patch) | |
| tree | c79494d5324cf7a800b0c7071e50e144eec83a81 /fs/crypto/keysetup.c | |
| parent | fscrypt: compute max_lblk_bits from s_maxbytes and block size (diff) | |
| download | linux-7a0263dc904f3467f474e4088ae092eda9a5a99b.tar.xz linux-7a0263dc904f3467f474e4088ae092eda9a5a99b.zip | |
fscrypt: replace get_ino_and_lblk_bits with just has_32bit_inodes
Now that fs/crypto/ computes the filesystem's lblk_bits from its maximum
file size, it is no longer necessary for filesystems to provide
lblk_bits via fscrypt_operations::get_ino_and_lblk_bits.
It is still necessary for fs/crypto/ to retrieve ino_bits from the
filesystem. However, this is used only to decide whether inode numbers
fit in 32 bits. Also, ino_bits is static for all relevant filesystems,
i.e. it doesn't depend on the filesystem instance.
Therefore, in the interest of keeping things as simple as possible,
replace 'get_ino_and_lblk_bits' with a flag 'has_32bit_inodes'. This
can always be changed back to a function if a filesystem needs it to be
dynamic, but for now a static flag is all that's needed.
Link: https://lore.kernel.org/r/20230925055451.59499-5-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@google.com>
Diffstat (limited to 'fs/crypto/keysetup.c')
0 files changed, 0 insertions, 0 deletions