Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

vfs: vfs-level fiemap interface

Basic vfs-level fiemap infrastructure, which sets up a new ->fiemap
inode operation.

Userspace can get extent information on a file via fiemap ioctl. As input,
the fiemap ioctl takes a struct fiemap which includes an array of struct
fiemap_extent (fm_extents). Size of the extent array is passed as
fm_extent_count and number of extents returned will be written into
fm_mapped_extents. Offset and length fields on the fiemap structure
(fm_start, fm_length) describe a logical range which will be searched for
extents. All extents returned will at least partially contain this range.
The actual extent offsets and ranges returned will be unmodified from their
offset and range on-disk.

The fiemap ioctl returns '0' on success. On error, -1 is returned and errno
is set. If errno is equal to EBADR, then fm_flags will contain those flags
which were passed in which the kernel did not understand. On all other
errors, the contents of fm_extents is undefined.

As fiemap evolved, there have been many authors of the vfs patch. As far as
I can tell, the list includes:
Kalpak Shah <kalpak.shah@sun.com>
Andreas Dilger <adilger@sun.com>
Eric Sandeen <sandeen@redhat.com>
Mark Fasheh <mfasheh@suse.com>

Signed-off-by: Mark Fasheh <mfasheh@suse.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: Michael Kerrisk <mtk.manpages@googlemail.com>
Cc: linux-api@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org

authored by

Mark Fasheh and committed by
Theodore Ts'o
c4b929b8 4d20c685

+465
+228
Documentation/filesystems/fiemap.txt
··· 1 + ============ 2 + Fiemap Ioctl 3 + ============ 4 + 5 + The fiemap ioctl is an efficient method for userspace to get file 6 + extent mappings. Instead of block-by-block mapping (such as bmap), fiemap 7 + returns a list of extents. 8 + 9 + 10 + Request Basics 11 + -------------- 12 + 13 + A fiemap request is encoded within struct fiemap: 14 + 15 + struct fiemap { 16 + __u64 fm_start; /* logical offset (inclusive) at 17 + * which to start mapping (in) */ 18 + __u64 fm_length; /* logical length of mapping which 19 + * userspace cares about (in) */ 20 + __u32 fm_flags; /* FIEMAP_FLAG_* flags for request (in/out) */ 21 + __u32 fm_mapped_extents; /* number of extents that were 22 + * mapped (out) */ 23 + __u32 fm_extent_count; /* size of fm_extents array (in) */ 24 + __u32 fm_reserved; 25 + struct fiemap_extent fm_extents[0]; /* array of mapped extents (out) */ 26 + }; 27 + 28 + 29 + fm_start, and fm_length specify the logical range within the file 30 + which the process would like mappings for. Extents returned mirror 31 + those on disk - that is, the logical offset of the 1st returned extent 32 + may start before fm_start, and the range covered by the last returned 33 + extent may end after fm_length. All offsets and lengths are in bytes. 34 + 35 + Certain flags to modify the way in which mappings are looked up can be 36 + set in fm_flags. If the kernel doesn't understand some particular 37 + flags, it will return EBADR and the contents of fm_flags will contain 38 + the set of flags which caused the error. If the kernel is compatible 39 + with all flags passed, the contents of fm_flags will be unmodified. 40 + It is up to userspace to determine whether rejection of a particular 41 + flag is fatal to it's operation. This scheme is intended to allow the 42 + fiemap interface to grow in the future but without losing 43 + compatibility with old software. 44 + 45 + fm_extent_count specifies the number of elements in the fm_extents[] array 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 48 + fm_mapped_extents count will hold the number of extents needed in 49 + fm_extents[] to hold the file's current mapping. Note that there is 50 + nothing to prevent the file from changing between calls to FIEMAP. 51 + 52 + The following flags can be set in fm_flags: 53 + 54 + * FIEMAP_FLAG_SYNC 55 + If this flag is set, the kernel will sync the file before mapping extents. 56 + 57 + * FIEMAP_FLAG_XATTR 58 + If this flag is set, the extents returned will describe the inodes 59 + extended attribute lookup tree, instead of it's data tree. 60 + 61 + 62 + Extent Mapping 63 + -------------- 64 + 65 + Extent information is returned within the embedded fm_extents array 66 + which userspace must allocate along with the fiemap structure. The 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 69 + returned via fm_mapped_extents. If the number of fiemap_extents 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 73 + fm_extent_count. In that case, the last extent in the array will not 74 + complete the requested range and will not have the FIEMAP_EXTENT_LAST 75 + flag set (see the next section on extent flags). 76 + 77 + Each extent is described by a single fiemap_extent structure as 78 + returned in fm_extents. 79 + 80 + struct fiemap_extent { 81 + __u64 fe_logical; /* logical offset in bytes for the start of 82 + * the extent */ 83 + __u64 fe_physical; /* physical offset in bytes for the start 84 + * of the extent */ 85 + __u64 fe_length; /* length in bytes for the extent */ 86 + __u64 fe_reserved64[2]; 87 + __u32 fe_flags; /* FIEMAP_EXTENT_* flags for this extent */ 88 + __u32 fe_reserved[3]; 89 + }; 90 + 91 + All offsets and lengths are in bytes and mirror those on disk. It is valid 92 + for an extents logical offset to start before the request or it's logical 93 + length to extend past the request. Unless FIEMAP_EXTENT_NOT_ALIGNED is 94 + returned, fe_logical, fe_physical, and fe_length will be aligned to the 95 + block size of the file system. With the exception of extents flagged as 96 + FIEMAP_EXTENT_MERGED, adjacent extents will not be merged. 97 + 98 + The fe_flags field contains flags which describe the extent returned. 99 + A special flag, FIEMAP_EXTENT_LAST is always set on the last extent in 100 + the file so that the process making fiemap calls can determine when no 101 + more extents are available, without having to call the ioctl again. 102 + 103 + Some flags are intentionally vague and will always be set in the 104 + presence of other more specific flags. This way a program looking for 105 + a general property does not have to know all existing and future flags 106 + which imply that property. 107 + 108 + For example, if FIEMAP_EXTENT_DATA_INLINE or FIEMAP_EXTENT_DATA_TAIL 109 + are set, FIEMAP_EXTENT_NOT_ALIGNED will also be set. A program looking 110 + for inline or tail-packed data can key on the specific flag. Software 111 + which simply cares not to try operating on non-aligned extents 112 + however, can just key on FIEMAP_EXTENT_NOT_ALIGNED, and not have to 113 + worry about all present and future flags which might imply unaligned 114 + data. Note that the opposite is not true - it would be valid for 115 + FIEMAP_EXTENT_NOT_ALIGNED to appear alone. 116 + 117 + * FIEMAP_EXTENT_LAST 118 + This is the last extent in the file. A mapping attempt past this 119 + extent will return nothing. 120 + 121 + * FIEMAP_EXTENT_UNKNOWN 122 + The location of this extent is currently unknown. This may indicate 123 + the data is stored on an inaccessible volume or that no storage has 124 + been allocated for the file yet. 125 + 126 + * FIEMAP_EXTENT_DELALLOC 127 + - This will also set FIEMAP_EXTENT_UNKNOWN. 128 + Delayed allocation - while there is data for this extent, it's 129 + physical location has not been allocated yet. 130 + 131 + * FIEMAP_EXTENT_ENCODED 132 + This extent does not consist of plain filesystem blocks but is 133 + encoded (e.g. encrypted or compressed). Reading the data in this 134 + extent via I/O to the block device will have undefined results. 135 + 136 + Note that it is *always* undefined to try to update the data 137 + in-place by writing to the indicated location without the 138 + assistance of the filesystem, or to access the data using the 139 + information returned by the FIEMAP interface while the filesystem 140 + is mounted. In other words, user applications may only read the 141 + extent data via I/O to the block device while the filesystem is 142 + unmounted, and then only if the FIEMAP_EXTENT_ENCODED flag is 143 + clear; user applications must not try reading or writing to the 144 + filesystem via the block device under any other circumstances. 145 + 146 + * FIEMAP_EXTENT_DATA_ENCRYPTED 147 + - This will also set FIEMAP_EXTENT_ENCODED 148 + The data in this extent has been encrypted by the file system. 149 + 150 + * FIEMAP_EXTENT_NOT_ALIGNED 151 + Extent offsets and length are not guaranteed to be block aligned. 152 + 153 + * FIEMAP_EXTENT_DATA_INLINE 154 + This will also set FIEMAP_EXTENT_NOT_ALIGNED 155 + Data is located within a meta data block. 156 + 157 + * FIEMAP_EXTENT_DATA_TAIL 158 + This will also set FIEMAP_EXTENT_NOT_ALIGNED 159 + Data is packed into a block with data from other files. 160 + 161 + * FIEMAP_EXTENT_UNWRITTEN 162 + Unwritten extent - the extent is allocated but it's data has not been 163 + initialized. This indicates the extent's data will be all zero if read 164 + through the filesystem but the contents are undefined if read directly from 165 + the device. 166 + 167 + * FIEMAP_EXTENT_MERGED 168 + This will be set when a file does not support extents, i.e., it uses a block 169 + based addressing scheme. Since returning an extent for each block back to 170 + userspace would be highly inefficient, the kernel will try to merge most 171 + adjacent blocks into 'extents'. 172 + 173 + 174 + VFS -> File System Implementation 175 + --------------------------------- 176 + 177 + File systems wishing to support fiemap must implement a ->fiemap callback on 178 + their inode_operations structure. The fs ->fiemap call is responsible for 179 + defining it's set of supported fiemap flags, and calling a helper function on 180 + each discovered extent: 181 + 182 + struct inode_operations { 183 + ... 184 + 185 + int (*fiemap)(struct inode *, struct fiemap_extent_info *, u64 start, 186 + u64 len); 187 + 188 + ->fiemap is passed struct fiemap_extent_info which describes the 189 + fiemap request: 190 + 191 + struct fiemap_extent_info { 192 + unsigned int fi_flags; /* Flags as passed from user */ 193 + unsigned int fi_extents_mapped; /* Number of mapped extents */ 194 + unsigned int fi_extents_max; /* Size of fiemap_extent array */ 195 + struct fiemap_extent *fi_extents_start; /* Start of fiemap_extent array */ 196 + }; 197 + 198 + It is intended that the file system should not need to access any of this 199 + structure directly. 200 + 201 + 202 + Flag checking should be done at the beginning of the ->fiemap callback via the 203 + fiemap_check_flags() helper: 204 + 205 + int fiemap_check_flags(struct fiemap_extent_info *fieinfo, u32 fs_flags); 206 + 207 + The struct fieinfo should be passed in as recieved from ioctl_fiemap(). The 208 + set of fiemap flags which the fs understands should be passed via fs_flags. If 209 + fiemap_check_flags finds invalid user flags, it will place the bad values in 210 + fieinfo->fi_flags and return -EBADR. If the file system gets -EBADR, from 211 + fiemap_check_flags(), it should immediately exit, returning that error back to 212 + ioctl_fiemap(). 213 + 214 + 215 + For each extent in the request range, the file system should call 216 + the helper function, fiemap_fill_next_extent(): 217 + 218 + int fiemap_fill_next_extent(struct fiemap_extent_info *info, u64 logical, 219 + u64 phys, u64 len, u32 flags, u32 dev); 220 + 221 + fiemap_fill_next_extent() will use the passed values to populate the 222 + next free extent in the fm_extents array. 'General' extent flags will 223 + automatically be set from specific flags on behalf of the calling file 224 + system so that the userspace API is not broken. 225 + 226 + fiemap_fill_next_extent() returns 0 on success, and 1 when the 227 + user-supplied fm_extents array is full. If an error is encountered 228 + while copying the extent to user memory, -EFAULT will be returned.
+155
fs/ioctl.c
··· 16 16 17 17 #include <asm/ioctls.h> 18 18 19 + /* So that the fiemap access checks can't overflow on 32 bit machines. */ 20 + #define FIEMAP_MAX_EXTENTS (UINT_MAX / sizeof(struct fiemap_extent)) 21 + 19 22 /** 20 23 * vfs_ioctl - call filesystem specific ioctl methods 21 24 * @filp: open file to invoke ioctl method on ··· 74 71 return put_user(res, p); 75 72 } 76 73 74 + /** 75 + * fiemap_fill_next_extent - Fiemap helper function 76 + * @fieinfo: Fiemap context passed into ->fiemap 77 + * @logical: Extent logical start offset, in bytes 78 + * @phys: Extent physical start offset, in bytes 79 + * @len: Extent length, in bytes 80 + * @flags: FIEMAP_EXTENT flags that describe this extent 81 + * 82 + * Called from file system ->fiemap callback. Will populate extent 83 + * info as passed in via arguments and copy to user memory. On 84 + * success, extent count on fieinfo is incremented. 85 + * 86 + * Returns 0 on success, -errno on error, 1 if this was the last 87 + * extent that will fit in user array. 88 + */ 89 + #define SET_UNKNOWN_FLAGS (FIEMAP_EXTENT_DELALLOC) 90 + #define SET_NO_UNMOUNTED_IO_FLAGS (FIEMAP_EXTENT_DATA_ENCRYPTED) 91 + #define SET_NOT_ALIGNED_FLAGS (FIEMAP_EXTENT_DATA_TAIL|FIEMAP_EXTENT_DATA_INLINE) 92 + int fiemap_fill_next_extent(struct fiemap_extent_info *fieinfo, u64 logical, 93 + u64 phys, u64 len, u32 flags) 94 + { 95 + struct fiemap_extent extent; 96 + struct fiemap_extent *dest = fieinfo->fi_extents_start; 97 + 98 + /* only count the extents */ 99 + if (fieinfo->fi_extents_max == 0) { 100 + fieinfo->fi_extents_mapped++; 101 + return (flags & FIEMAP_EXTENT_LAST) ? 1 : 0; 102 + } 103 + 104 + if (fieinfo->fi_extents_mapped >= fieinfo->fi_extents_max) 105 + return 1; 106 + 107 + if (flags & SET_UNKNOWN_FLAGS) 108 + flags |= FIEMAP_EXTENT_UNKNOWN; 109 + if (flags & SET_NO_UNMOUNTED_IO_FLAGS) 110 + flags |= FIEMAP_EXTENT_ENCODED; 111 + if (flags & SET_NOT_ALIGNED_FLAGS) 112 + flags |= FIEMAP_EXTENT_NOT_ALIGNED; 113 + 114 + memset(&extent, 0, sizeof(extent)); 115 + extent.fe_logical = logical; 116 + extent.fe_physical = phys; 117 + extent.fe_length = len; 118 + extent.fe_flags = flags; 119 + 120 + dest += fieinfo->fi_extents_mapped; 121 + if (copy_to_user(dest, &extent, sizeof(extent))) 122 + return -EFAULT; 123 + 124 + fieinfo->fi_extents_mapped++; 125 + if (fieinfo->fi_extents_mapped == fieinfo->fi_extents_max) 126 + return 1; 127 + return (flags & FIEMAP_EXTENT_LAST) ? 1 : 0; 128 + } 129 + EXPORT_SYMBOL(fiemap_fill_next_extent); 130 + 131 + /** 132 + * fiemap_check_flags - check validity of requested flags for fiemap 133 + * @fieinfo: Fiemap context passed into ->fiemap 134 + * @fs_flags: Set of fiemap flags that the file system understands 135 + * 136 + * Called from file system ->fiemap callback. This will compute the 137 + * intersection of valid fiemap flags and those that the fs supports. That 138 + * value is then compared against the user supplied flags. In case of bad user 139 + * flags, the invalid values will be written into the fieinfo structure, and 140 + * -EBADR is returned, which tells ioctl_fiemap() to return those values to 141 + * userspace. For this reason, a return code of -EBADR should be preserved. 142 + * 143 + * Returns 0 on success, -EBADR on bad flags. 144 + */ 145 + int fiemap_check_flags(struct fiemap_extent_info *fieinfo, u32 fs_flags) 146 + { 147 + u32 incompat_flags; 148 + 149 + incompat_flags = fieinfo->fi_flags & ~(FIEMAP_FLAGS_COMPAT & fs_flags); 150 + if (incompat_flags) { 151 + fieinfo->fi_flags = incompat_flags; 152 + return -EBADR; 153 + } 154 + return 0; 155 + } 156 + EXPORT_SYMBOL(fiemap_check_flags); 157 + 158 + static int fiemap_check_ranges(struct super_block *sb, 159 + u64 start, u64 len, u64 *new_len) 160 + { 161 + *new_len = len; 162 + 163 + if (len == 0) 164 + return -EINVAL; 165 + 166 + if (start > sb->s_maxbytes) 167 + return -EFBIG; 168 + 169 + /* 170 + * Shrink request scope to what the fs can actually handle. 171 + */ 172 + if ((len > sb->s_maxbytes) || 173 + (sb->s_maxbytes - len) < start) 174 + *new_len = sb->s_maxbytes - start; 175 + 176 + return 0; 177 + } 178 + 179 + static int ioctl_fiemap(struct file *filp, unsigned long arg) 180 + { 181 + struct fiemap fiemap; 182 + struct fiemap_extent_info fieinfo = { 0, }; 183 + struct inode *inode = filp->f_path.dentry->d_inode; 184 + struct super_block *sb = inode->i_sb; 185 + u64 len; 186 + int error; 187 + 188 + if (!inode->i_op->fiemap) 189 + return -EOPNOTSUPP; 190 + 191 + if (copy_from_user(&fiemap, (struct fiemap __user *)arg, 192 + sizeof(struct fiemap))) 193 + return -EFAULT; 194 + 195 + if (fiemap.fm_extent_count > FIEMAP_MAX_EXTENTS) 196 + return -EINVAL; 197 + 198 + error = fiemap_check_ranges(sb, fiemap.fm_start, fiemap.fm_length, 199 + &len); 200 + if (error) 201 + return error; 202 + 203 + fieinfo.fi_flags = fiemap.fm_flags; 204 + fieinfo.fi_extents_max = fiemap.fm_extent_count; 205 + fieinfo.fi_extents_start = (struct fiemap_extent *)(arg + sizeof(fiemap)); 206 + 207 + if (fiemap.fm_extent_count != 0 && 208 + !access_ok(VERIFY_WRITE, fieinfo.fi_extents_start, 209 + fieinfo.fi_extents_max * sizeof(struct fiemap_extent))) 210 + return -EFAULT; 211 + 212 + if (fieinfo.fi_flags & FIEMAP_FLAG_SYNC) 213 + filemap_write_and_wait(inode->i_mapping); 214 + 215 + error = inode->i_op->fiemap(inode, &fieinfo, fiemap.fm_start, len); 216 + fiemap.fm_flags = fieinfo.fi_flags; 217 + fiemap.fm_mapped_extents = fieinfo.fi_extents_mapped; 218 + if (copy_to_user((char *)arg, &fiemap, sizeof(fiemap))) 219 + error = -EFAULT; 220 + 221 + return error; 222 + } 223 + 77 224 static int file_ioctl(struct file *filp, unsigned int cmd, 78 225 unsigned long arg) 79 226 { ··· 233 80 switch (cmd) { 234 81 case FIBMAP: 235 82 return ioctl_fibmap(filp, p); 83 + case FS_IOC_FIEMAP: 84 + return ioctl_fiemap(filp, arg); 236 85 case FIGETBSZ: 237 86 return put_user(inode->i_sb->s_blocksize, p); 238 87 case FIONREAD:
+64
include/linux/fiemap.h
··· 1 + /* 2 + * FS_IOC_FIEMAP ioctl infrastructure. 3 + * 4 + * Some portions copyright (C) 2007 Cluster File Systems, Inc 5 + * 6 + * Authors: Mark Fasheh <mfasheh@suse.com> 7 + * Kalpak Shah <kalpak.shah@sun.com> 8 + * Andreas Dilger <adilger@sun.com> 9 + */ 10 + 11 + #ifndef _LINUX_FIEMAP_H 12 + #define _LINUX_FIEMAP_H 13 + 14 + struct fiemap_extent { 15 + __u64 fe_logical; /* logical offset in bytes for the start of 16 + * the extent from the beginning of the file */ 17 + __u64 fe_physical; /* physical offset in bytes for the start 18 + * of the extent from the beginning of the disk */ 19 + __u64 fe_length; /* length in bytes for this extent */ 20 + __u64 fe_reserved64[2]; 21 + __u32 fe_flags; /* FIEMAP_EXTENT_* flags for this extent */ 22 + __u32 fe_reserved[3]; 23 + }; 24 + 25 + struct fiemap { 26 + __u64 fm_start; /* logical offset (inclusive) at 27 + * which to start mapping (in) */ 28 + __u64 fm_length; /* logical length of mapping which 29 + * userspace wants (in) */ 30 + __u32 fm_flags; /* FIEMAP_FLAG_* flags for request (in/out) */ 31 + __u32 fm_mapped_extents;/* number of extents that were mapped (out) */ 32 + __u32 fm_extent_count; /* size of fm_extents array (in) */ 33 + __u32 fm_reserved; 34 + struct fiemap_extent fm_extents[0]; /* array of mapped extents (out) */ 35 + }; 36 + 37 + #define FIEMAP_MAX_OFFSET (~0ULL) 38 + 39 + #define FIEMAP_FLAG_SYNC 0x00000001 /* sync file data before map */ 40 + #define FIEMAP_FLAG_XATTR 0x00000002 /* map extended attribute tree */ 41 + 42 + #define FIEMAP_FLAGS_COMPAT (FIEMAP_FLAG_SYNC | FIEMAP_FLAG_XATTR) 43 + 44 + #define FIEMAP_EXTENT_LAST 0x00000001 /* Last extent in file. */ 45 + #define FIEMAP_EXTENT_UNKNOWN 0x00000002 /* Data location unknown. */ 46 + #define FIEMAP_EXTENT_DELALLOC 0x00000004 /* Location still pending. 47 + * Sets EXTENT_UNKNOWN. */ 48 + #define FIEMAP_EXTENT_ENCODED 0x00000008 /* Data can not be read 49 + * while fs is unmounted */ 50 + #define FIEMAP_EXTENT_DATA_ENCRYPTED 0x00000080 /* Data is encrypted by fs. 51 + * Sets EXTENT_NO_BYPASS. */ 52 + #define FIEMAP_EXTENT_NOT_ALIGNED 0x00000100 /* Extent offsets may not be 53 + * block aligned. */ 54 + #define FIEMAP_EXTENT_DATA_INLINE 0x00000200 /* Data mixed with metadata. 55 + * Sets EXTENT_NOT_ALIGNED.*/ 56 + #define FIEMAP_EXTENT_DATA_TAIL 0x00000400 /* Multiple files in block. 57 + * Sets EXTENT_NOT_ALIGNED.*/ 58 + #define FIEMAP_EXTENT_UNWRITTEN 0x00000800 /* Space allocated, but 59 + * no data (i.e. zero). */ 60 + #define FIEMAP_EXTENT_MERGED 0x00001000 /* File does not natively 61 + * support extents. Result 62 + * merged for efficiency. */ 63 + 64 + #endif /* _LINUX_FIEMAP_H */
+18
include/linux/fs.h
··· 231 231 #define FS_IOC_SETFLAGS _IOW('f', 2, long) 232 232 #define FS_IOC_GETVERSION _IOR('v', 1, long) 233 233 #define FS_IOC_SETVERSION _IOW('v', 2, long) 234 + #define FS_IOC_FIEMAP _IOWR('f', 11, struct fiemap) 234 235 #define FS_IOC32_GETFLAGS _IOR('f', 1, int) 235 236 #define FS_IOC32_SETFLAGS _IOW('f', 2, int) 236 237 #define FS_IOC32_GETVERSION _IOR('v', 1, int) ··· 292 291 #include <linux/mutex.h> 293 292 #include <linux/capability.h> 294 293 #include <linux/semaphore.h> 294 + #include <linux/fiemap.h> 295 295 296 296 #include <asm/atomic.h> 297 297 #include <asm/byteorder.h> ··· 1181 1179 extern int file_permission(struct file *, int); 1182 1180 1183 1181 /* 1182 + * VFS FS_IOC_FIEMAP helper definitions. 1183 + */ 1184 + struct fiemap_extent_info { 1185 + unsigned int fi_flags; /* Flags as passed from user */ 1186 + unsigned int fi_extents_mapped; /* Number of mapped extents */ 1187 + unsigned int fi_extents_max; /* Size of fiemap_extent array */ 1188 + struct fiemap_extent *fi_extents_start; /* Start of fiemap_extent 1189 + * array */ 1190 + }; 1191 + int fiemap_fill_next_extent(struct fiemap_extent_info *info, u64 logical, 1192 + u64 phys, u64 len, u32 flags); 1193 + int fiemap_check_flags(struct fiemap_extent_info *fieinfo, u32 fs_flags); 1194 + 1195 + /* 1184 1196 * File types 1185 1197 * 1186 1198 * NOTE! These match bits 12..15 of stat.st_mode ··· 1303 1287 void (*truncate_range)(struct inode *, loff_t, loff_t); 1304 1288 long (*fallocate)(struct inode *inode, int mode, loff_t offset, 1305 1289 loff_t len); 1290 + int (*fiemap)(struct inode *, struct fiemap_extent_info *, u64 start, 1291 + u64 len); 1306 1292 }; 1307 1293 1308 1294 struct seq_file;