diff options
| author | Ritesh Harjani <riteshh@linux.ibm.com> | 2020-02-28 14:56:57 +0530 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2020-03-14 14:43:12 -0400 |
| commit | b2c5764262edded1b1cfff5a6ca82c3d61bb4a4a (patch) | |
| tree | 24cb92726094661481c9a62bb4ed11c02ffc4d0c /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | ac58e4fb03f9d111d733a4ad379d06eef3a24705 (diff) | |
ext4: make ext4_ind_map_blocks work with fiemap
For indirect block mapping if the i_block > max supported block in inode
then ext4_ind_map_blocks() returns a -EIO error. But in case of fiemap
this could be a valid query to ->iomap_begin call.
So check if the offset >= s_bitmap_maxbytes in ext4_iomap_begin_report(),
then simply skip calling ext4_map_blocks().
Signed-off-by: Ritesh Harjani <riteshh@linux.ibm.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Link: https://lore.kernel.org/r/87fa0ddc5967fa707656212a3b66a7233425325c.1582880246.git.riteshh@linux.ibm.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions