Lines Matching refs:be

35 Certain flags to modify the way in which mappings are looked up can be
39 with all flags passed, the contents of fm_flags will be unmodified.
46 that can be used to return extents.  If fm_extent_count is zero, then the
47 fm_extents[] array is ignored (no extents will be returned), and the
52 The following flags can be set in fm_flags:
67 number of elements in the fiemap_extents[] array should be passed via
68 fm_extent_count. The number of extents mapped by kernel will be
70 allocated is less than would be required to map the requested range,
71 the maximum number of extents that can be mapped in the fm_extent[]
72 array will be returned and fm_mapped_extents will be equal to
94 returned, fe_logical, fe_physical, and fe_length will be aligned to the
96 FIEMAP_EXTENT_MERGED, adjacent extents will not be merged.
103 Some flags are intentionally vague and will always be set in the
109 are set, FIEMAP_EXTENT_NOT_ALIGNED will also be set. A program looking
114 data. Note that the opposite is not true - it would be valid for
151 Extent offsets and length are not guaranteed to be block aligned.
163 initialized.  This indicates the extent's data will be all zero if read
168 This will be set when a file does not support extents, i.e., it uses a block
170 userspace would be highly inefficient, the kernel will try to merge most
199 structure directly. Filesystem handlers should be tolerant to signals and return
203 Flag checking should be done at the beginning of the ->fiemap callback via the
208 The struct fieinfo should be passed in as received from ioctl_fiemap(). The
209 set of fiemap flags which the fs understands should be passed via fs_flags. If
224 automatically be set from specific flags on behalf of the calling file
229 while copying the extent to user memory, -EFAULT will be returned.