Error handling in unpin_extent_cache()
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | brtfs: handle errors returned from unpin_extent_cache()fs/ fs/ | +16 | 0 replies | |
| 2/3 | btrfs: return errors from unpin_extent_range()fs/ fs/ | +16 | 0 replies | |
| 3/3 | btrfs: make btrfs_error_unpin_extent_range() return voidfs/ fs/ | +7 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Error handling in unpin_extent_cache()
Do the erorr handling in unpin_extent_cache so we don't se any "change the return value to void" patches again. The errors are pushed up one level in each patch.
There's case in btrfs_finish_extent_commit() that still needs to be changed from BUG_ON to proper handling but it does not look easy.
David Sterba (3):
brtfs: handle errors returned from unpin_extent_cache()
btrfs: return errors from unpin_extent_range()
btrfs: make btrfs_error_unpin_extent_range() return void
fs/btrfs/block-group.c | 2 +- fs/btrfs/ctree.h | 3 +-- fs/btrfs/extent-tree.c | 22 ++++++++++++++++------ fs/btrfs/extent_map.c | 10 +++++++++- fs/btrfs/inode.c | 9 +++++++-- 5 files changed, 34 insertions(+), 12 deletions(-)
Signature · 1 line
2.42.1