Searched refs:log2_data_unit_size (Results 1 – 5 of 5) sorted by relevance
249 if (policy->log2_data_unit_size) { in fscrypt_supported_v2_policy()255 if (policy->log2_data_unit_size > inode->i_blkbits || in fscrypt_supported_v2_policy()256 policy->log2_data_unit_size < SECTOR_SHIFT /* 9 */) { in fscrypt_supported_v2_policy()259 policy->log2_data_unit_size); in fscrypt_supported_v2_policy()262 if (policy->log2_data_unit_size != inode->i_blkbits && in fscrypt_supported_v2_policy()360 ctx->log2_data_unit_size = policy->log2_data_unit_size; in fscrypt_new_context()421 policy->log2_data_unit_size = ctx->log2_data_unit_size; in fscrypt_policy_from_context()
86 u8 log2_data_unit_size; member209 return policy->log2_data_unit_size ?: inode->i_blkbits; in fscrypt_policy_v2_du_bits()
74 __u8 log2_data_unit_size; member
485 a sub-block data unit size via the ``log2_data_unit_size`` field of593 __u8 log2_data_unit_size;636 - ``log2_data_unit_size`` is the log2 of the data unit size in bytes,639 ``log2_data_unit_size`` to 12 causes file contents be passed to the643 Not all filesystems support setting ``log2_data_unit_size``. ext4649 The main use case for ``log2_data_unit_size`` is for selecting a1473 u8 log2_data_unit_size;