From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/3] Error handling in unpin_extent_cache()
Date: Tue, 16 Jan 2024 18:42:46 +0100 [thread overview]
Message-ID: <cover.1705426614.git.dsterba@suse.com> (raw)
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(-)
--
2.42.1
next reply other threads:[~2024-01-16 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 17:42 David Sterba [this message]
2024-01-16 17:42 ` [PATCH 1/3] brtfs: handle errors returned from unpin_extent_cache() David Sterba
2024-01-16 17:42 ` [PATCH 2/3] btrfs: return errors from unpin_extent_range() David Sterba
2024-01-16 17:42 ` [PATCH 3/3] btrfs: make btrfs_error_unpin_extent_range() return void David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1705426614.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox