summaryrefslogtreecommitdiffstats
path: root/security/keys
diff options
context:
space:
mode:
authorFilipe David Borba Manana <fdmanana@gmail.com>2013-10-01 17:06:53 +0100
committerChris Mason <chris.mason@fusionio.com>2013-11-11 21:55:11 -0500
commit3d41d70252234db153ea1b037052278ff5786ad5 (patch)
tree7bd2c8d5c7a6fcb2e25a25204c525bf18d0535aa /security/keys
parent6174d3cb43aa974d0c8590a3e628ac35ab0bbc13 (diff)
downloadop-kernel-dev-3d41d70252234db153ea1b037052278ff5786ad5.zip
op-kernel-dev-3d41d70252234db153ea1b037052278ff5786ad5.tar.gz
Btrfs: remove unnecessary tree search when logging inode
In tree-log.c:btrfs_log_inode(), we keep calling btrfs_search_forward() until it returns a key whose objectid is higher than our inode or until the key's type is higher than our maximum allowed type. At the end of the loop, we increment our mininum search key's objectid and type regardless of our desired target objectid and maximum desired type, which causes another loop iteration that will call again btrfs_search_forward() just to figure out we've gone beyond our maximum key and exit the loop. Therefore while incrementing our minimum key, don't do it blindly and exit the loop immiediately if the next search key's objectid or type is beyond what we seek. Also after incrementing the type, set the key's offset to 0, which was missing and could make us loose some of the inode's items. Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com> Signed-off-by: Josef Bacik <jbacik@fusionio.com> Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Diffstat (limited to 'security/keys')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud