summaryrefslogtreecommitdiffstats
path: root/net/bluetooth
diff options
context:
space:
mode:
authorJan Schmidt <list.btrfs@jan-o-sch.net>2012-06-22 14:52:13 +0200
committerJan Schmidt <list.btrfs@jan-o-sch.net>2012-06-27 16:34:40 +0200
commit19956c7e94a7a58d6df8c4db5ae62f9109a7c663 (patch)
tree4ff17f3a5f0cc91453298c5c494f8592ccfb3e50 /net/bluetooth
parent155725c9c051a343be5e555bf943da827e6cf721 (diff)
downloadlinux-19956c7e94a7a58d6df8c4db5ae62f9109a7c663.tar.gz
linux-19956c7e94a7a58d6df8c4db5ae62f9109a7c663.tar.bz2
linux-19956c7e94a7a58d6df8c4db5ae62f9109a7c663.zip
Btrfs: fix tree mod log rewind of ADD operations
When a MOD_LOG_KEY_ADD operation is rewinded, we remove the key from the tree block. If its not the last key, removal involves a move operation. This move operation was explicitly done before this commit. However, at insertion time, there's a move operation before the actual addition to make room for the new key, which is recorded in the tree mod log as well. This means, we must drop the move operation when rewinding the add operation, because the next operation we'll be rewinding will be the corresponding MOD_LOG_MOVE_KEYS operation. Signed-off-by: Jan Schmidt <list.btrfs@jan-o-sch.net>
Diffstat (limited to 'net/bluetooth')
0 files changed, 0 insertions, 0 deletions