Lines Matching +full:data +full:- +full:mapping

1 .. SPDX-License-Identifier: GPL-2.0
8 extent mappings. Instead of block-by-block mapping (such as bmap), fiemap
13 --------------
19 				  * which to start mapping (in) */
20 	__u64	fm_length;	 /* logical length of mapping which
33 those on disk - that is, the logical offset of the 1st returned extent
51 fm_extents[] to hold the file's current mapping.  Note that there is
57   If this flag is set, the kernel will sync the file before mapping extents.
61   extended attribute lookup tree, instead of its data tree.
64 Extent Mapping
65 --------------
112 for inline or tail-packed data can key on the specific flag. Software
113 which simply cares not to try operating on non-aligned extents
116 data. Note that the opposite is not true - it would be valid for
120   This is generally the last extent in the file. A mapping attempt past
123   (via fiemap->fm_length).
127   the data is stored on an inaccessible volume or that no storage has
133   Delayed allocation - while there is data for this extent, its
138   encoded (e.g. encrypted or compressed).  Reading the data in this
141 Note that it is *always* undefined to try to update the data
142 in-place by writing to the indicated location without the
143 assistance of the filesystem, or to access the data using the
146 extent data via I/O to the block device while the filesystem is
153   The data in this extent has been encrypted by the file system.
160   Data is located within a meta data block.
164   Data is packed into a block with data from other files.
167   Unwritten extent - the extent is allocated but its data has not been
168   initialized.  This indicates the extent's data will be all zero if read
179 VFS -> File System Implementation
180 ---------------------------------
182 File systems wishing to support fiemap must implement a ->fiemap callback on
183 their inode_operations structure. The fs ->fiemap call is responsible for
193 ->fiemap is passed struct fiemap_extent_info which describes the
208 Flag checking should be done at the beginning of the ->fiemap callback via the
217 fieinfo->fi_flags and return -EBADR. If the file system gets -EBADR, from
235 user-supplied fm_extents array is full. If an error is encountered
236 while copying the extent to user memory, -EFAULT will be returned.