diff options
author | Kent Overstreet <kent.overstreet@gmail.com> | 2022-03-12 16:14:55 -0500 |
---|---|---|
committer | Kent Overstreet <kent.overstreet@linux.dev> | 2023-10-22 17:09:27 -0400 |
commit | d13f9ee61dac0b5d663844c5778309ec8af1561f (patch) | |
tree | 32b5b88bf4f2bdddaef78b08d0de4a5a76eb16da /fs/bcachefs/extents.h | |
parent | 8570d775ca90192f8663ddd828a09d0c6698c71c (diff) | |
download | linux-d13f9ee61dac0b5d663844c5778309ec8af1561f.tar.gz linux-d13f9ee61dac0b5d663844c5778309ec8af1561f.tar.bz2 linux-d13f9ee61dac0b5d663844c5778309ec8af1561f.zip |
bcachefs: Revalidate pointer to old bkey val before calling mem triggers
We recently started stashing a copy of the key being overwritten in
btree_insert_entry: this is helpful for avoiding multiple calls to
bch2_btree_path_peek_slot() and bch2_journal_keys_peek() in the
transaction commit path.
But it turns out this has a problem - when we run mem/atomic triggers,
we've done a couple things that can invalidate the pointer to the old
key's value. This makes the optimization of stashing a pointer to the
old value questionable, but for now this patch revalidates that pointer
before running mem triggers.
Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>
Diffstat (limited to 'fs/bcachefs/extents.h')
0 files changed, 0 insertions, 0 deletions