diff options
| author | Qu Wenruo <[email protected]> | 2021-08-06 16:12:34 +0800 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2021-10-26 19:06:15 +0200 |
| commit | 76068cae634bf1bb3e06f79d7b879834277554ca (patch) | |
| tree | 30a2d33ea7df8c184339ba7ebe36582a6706902d /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | cae796868042e73fbda5056d2528cd0b815f9c08 (diff) | |
btrfs: defrag: replace hard coded PAGE_SIZE with sectorsize
When testing subpage defrag support, I always find some strange inode
nbytes error, after a lot of debugging, it turns out that
defrag_lookup_extent() is using PAGE_SIZE as size for
lookup_extent_mapping().
Since lookup_extent_mapping() is calling __lookup_extent_mapping() with
@strict == 1, this means any extent map smaller than one page will be
ignored, prevent subpage defrag to grab a correct extent map.
There are quite some PAGE_SIZE usage in ioctl.c, but most of them are
correct usages, and can be one of the following cases:
- ioctl structure size check
We want ioctl structure to be contained inside one page.
- real page operations
The remaining cases in defrag_lookup_extent() and
check_defrag_in_cache() will be addressed in this patch.
Signed-off-by: Qu Wenruo <[email protected]>
Reviewed-by: David Sterba <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions