bcachefs: iter->real_pos

Browse source

We need to differentiate between the search position of a btree
iterator, vs. what it actually points at (what we found). This matters
for extents, where iter->pos will typically be the start of the key we
found and iter->real_pos will be the end of the key we found (which soon
won't necessarily be in the same btree node!) and it will also matter
for snapshots.

Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>

...

This commit is contained in:

Kent Overstreet 2021-02-11 21:57:32 -05:00 • committed by Kent Overstreet

parent 9f631dc143

commit 7e1a3aa9df

3 changed files with 120 additions and 92 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

208

fs/bcachefs/btree_iter.c

View file

2

fs/bcachefs/btree_types.h

View file

2

fs/bcachefs/btree_update_leaf.c

View file