]> git.hungrycats.org Git - linux/commit
projects / linux / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 580e655) | patch
Btrfs: deal with error on secondary log properly
authorJosef Bacik <jbacik@fb.com>
Tue, 25 Aug 2015 17:01:40 +0000 (13:01 -0400)
committerZygo Blaxell <zblaxell@thirteen.furryterror.org>
Wed, 26 Aug 2015 01:22:40 +0000 (21:22 -0400)
commit6ebeedeb4589872bbae0c52b5981b3a87260543f
treebd4c37a4195a2401cd2d4ef0d79a834d66ca0c6btree | snapshot
parent580e655a4cf1b044b13fac0a845ef37e2ad2af1ccommit | diff
Btrfs: deal with error on secondary log properly

If we have an fsync at the same time in two seperate subvolumes we could end up
with the tree log pointing at invalid blocks.  We need to notice if our writeout
failed in anyway, if it did then we need to do a full transaction commit and
return an error on the subvolume that gave us the io error.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fb.com>
(cherry picked from commit d3e532cc080acaf30bac093998e4db4901cf690b)
fs/btrfs/file.c diff | blob | history
fs/btrfs/tree-log.c diff | blob | history
Linux kernels and configurations used by Zygo.