| Message ID | 20181128085456.5702-1-jthumshirn@suse.de (mailing list archive) |
|---|---|
| Headers | show |
| Series | Misc cosmetic changes for map_private_extent_buffer | expand |
On Wed, Nov 28, 2018 at 09:54:53AM +0100, Johannes Thumshirn wrote: > While trying to understand the checksum code I came across some oddities > regarding map_private_extent_buffer() and it's interaction with > csum_tree_block(). > > These patches address them but are either purely cosmetic or only add a > comment documenting behaviour. > > Changes to v1: > * Add Reviewed-by tags > * Change wording of commit message in patch 3/3 > > Johannes Thumshirn (3): > btrfs: don't initialize 'offset' in map_private_extent_buffer() > btrfs: use offset_in_page for start_offset in > map_private_extent_buffer() > btrfs: document extent mapping assumptions in checksum 1 and 3 applied, thanks.
While trying to understand the checksum code I came across some oddities regarding map_private_extent_buffer() and it's interaction with csum_tree_block(). These patches address them but are either purely cosmetic or only add a comment documenting behaviour. Changes to v1: * Add Reviewed-by tags * Change wording of commit message in patch 3/3 Johannes Thumshirn (3): btrfs: don't initialize 'offset' in map_private_extent_buffer() btrfs: use offset_in_page for start_offset in map_private_extent_buffer() btrfs: document extent mapping assumptions in checksum fs/btrfs/disk-io.c | 6 ++++++ fs/btrfs/extent_io.c | 4 ++-- 2 files changed, 8 insertions(+), 2 deletions(-)