Lines Matching refs:xattr
107 (no)user_xattr Setup Extended User Attributes. Note: xattr is enabled
228 Each share xattr can also be directly found by the following formula:
229 xattr offset = xattr_blkaddr * block_size + 4 * xattr_id
236 | ... | xattr_entry | xattr data | ... | xattr_entry | xattr data ...
283 The long xattr name prefixes feature is introduced to address this issue. The
284 overall idea is that, apart from the existing predefined prefixes, the xattr
285 entry could also refer to user-specified long xattr name prefixes, e.g.
288 When referring to a long xattr name prefix, the highest bit (bit 7) of
292 xattr name prefix is stored in erofs_xattr_entry.e_name, which could be empty if
293 the full xattr name matches exactly as its long xattr name prefix.
295 All long xattr prefixes are stored one by one in the packed inode as long as
298 long xattr name prefixes, while (xattr_prefix_start * 4) indicates the start
305 index of the predefined xattr name prefix, e.g. EROFS_XATTR_INDEX_TRUSTED for