summaryrefslogtreecommitdiff
path: root/fs/btrfs/Kconfig
diff options
context:
space:
mode:
authorFilipe David Borba Manana <fdmanana@gmail.com>2014-01-11 21:31:25 +0000
committerChris Mason <clm@fb.com>2014-01-28 13:20:30 -0800
commitc57c2b3ed248b3f1712e4172eb85b361199582f2 (patch)
tree7dc61c170e763cb469c0d11957152e702356093a /fs/btrfs/Kconfig
parentf499e40fd97698a1c48d188279647009b21905fe (diff)
Btrfs: unlock inodes in correct order in clone ioctl
In the clone ioctl, when the source and target inodes are different, we can acquire their mutexes in 2 possible different orders. After we're done cloning, we were releasing the mutexes always in the same order - the most correct way of doing it is to release them by the reverse order they were acquired. Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com> Signed-off-by: Josef Bacik <jbacik@fb.com> Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'fs/btrfs/Kconfig')
0 files changed, 0 insertions, 0 deletions