diff options
| author | Qu Wenruo <[email protected]> | 2021-05-31 16:50:37 +0800 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2021-06-21 15:19:09 +0200 |
| commit | 98af9ab12b49a5ae338b523e64b5a7dd637781d4 (patch) | |
| tree | d70d298440198fd34b51ca900b9c61aa4c379cec /scripts/gdb/linux/tasks.py | |
| parent | 968f2566ad897d643af66df0d44c070128402941 (diff) | |
btrfs: pass bytenr directly to __process_pages_contig()
As a preparation for incoming subpage support, we need bytenr passed to
__process_pages_contig() directly, not the current page index.
So change the parameter and all callers to pass bytenr in.
With the modification, here we need to replace the old @index_ret with
@processed_end for __process_pages_contig(), but this brings a small
problem.
Normally we follow the inclusive return value, meaning @processed_end
should be the last byte we processed.
If parameter @start is 0, and we failed to lock any page, then we would
return @processed_end as -1, causing more problems for
__unlock_for_delalloc().
So here for @processed_end, we use two different return value patterns.
If we have locked any page, @processed_end will be the last byte of
locked page.
Or it will be @start otherwise.
This change will impact lock_delalloc_pages(), so it needs to check
@processed_end to only unlock the range if we have locked any.
Tested-by: Ritesh Harjani <[email protected]> # [ppc64]
Tested-by: Anand Jain <[email protected]> # [aarch64]
Signed-off-by: Qu Wenruo <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/tasks.py')
0 files changed, 0 insertions, 0 deletions