diff options
author | Nikolay Borisov <nborisov@suse.com> | 2017-09-28 10:53:17 +0300 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2017-10-30 12:27:58 +0100 |
commit | 9417ebc8a676487c6ec8825f92fb28f7dbeb5f4b (patch) | |
tree | ad38ec9df2f1766b55a31df3c552d931b5ec3518 /fs/fscache | |
parent | 7132a262595a43abd483f1c5139afc038c67fbbb (diff) | |
download | linux-stable-9417ebc8a676487c6ec8825f92fb28f7dbeb5f4b.tar.gz linux-stable-9417ebc8a676487c6ec8825f92fb28f7dbeb5f4b.tar.bz2 linux-stable-9417ebc8a676487c6ec8825f92fb28f7dbeb5f4b.zip |
btrfs: Explicitly handle btrfs_update_root failure
btrfs_udpate_root can fail and it aborts the transaction, the correct
way to handle an aborted transaction is to explicitly end with
btrfs_end_transaction. Even now the code is correct since
btrfs_commit_transaction would handle an aborted transaction but this is
more of an implementation detail. So let's be explicit in handling
failure in btrfs_update_root.
Furthermore btrfs_commit_transaction can also fail and by ignoring it's
return value we could have left the in-memory copy of the root item in
an inconsistent state. So capture the error value which allows us to
correctly revert the RO/RW flags in case of commit failure.
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/fscache')
0 files changed, 0 insertions, 0 deletions