projects / GitHub / LineageOS / android_kernel_motorola_exynos9610.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: bc17862) | patch
Btrfs: return EIO if we have extent tree corruption
authorJosef Bacik <jbacik@fusionio.com>
Fri, 8 Mar 2013 20:41:02 +0000 (15:41 -0500)
committerChris Mason <chris.mason@fusionio.com>
Thu, 14 Mar 2013 18:57:29 +0000 (14:57 -0400)
commit492104c866cb1b62a11393adccb477f5cd2c7768
tree1aacf5abaf22d0a591b4cb39e494c95694fb589ctree | snapshot (tar.gz zip)
parentbc178622d40d87e75abc131007342429c9b03351commit | diff
Btrfs: return EIO if we have extent tree corruption

The callers of lookup_inline_extent_info all handle getting an error back
properly, so return an error if we have corruption instead of being a jerk and
panicing.  Still WARN_ON() since this is kind of crucial and I've been seeing it
a bit too much recently for my taste, I think we're doing something wrong
somewhere.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
fs/btrfs/extent-tree.c diff | blob | blame | history