From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/5] Error handling fixes
Date: Wed, 19 Jun 2024 19:08:50 +0200 [thread overview]
Message-ID: <cover.1718816796.git.dsterba@suse.com> (raw)
A few replacements of btrfs_handle_fs_error() with transaction abort or
other means.
David Sterba (5):
btrfs: abort transaction if we don't find extref in
btrfs_del_inode_extref()
btrfs: only print error message when checking item size in
print_extent_item()
btrfs: abort transaction on errors in btrfs_free_chunk()
btrfs: qgroup: preallocate memory before adding a relation
btrfs: qgroup: warn about inconsistent qgroups when relation update
fails
fs/btrfs/inode-item.c | 4 ++--
fs/btrfs/ioctl.c | 25 +++++++++++++++++++------
fs/btrfs/print-tree.c | 2 +-
fs/btrfs/qgroup.c | 25 ++++++++-----------------
fs/btrfs/qgroup.h | 11 ++++++++++-
fs/btrfs/volumes.c | 15 +++++++++------
6 files changed, 49 insertions(+), 33 deletions(-)
--
2.45.0
next reply other threads:[~2024-06-19 17:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 17:08 David Sterba [this message]
2024-06-19 17:08 ` [PATCH 1/5] btrfs: abort transaction if we don't find extref in btrfs_del_inode_extref() David Sterba
2024-06-19 17:09 ` [PATCH 2/5] btrfs: only print error message when checking item size in print_extent_item() David Sterba
2024-06-19 17:09 ` [PATCH 3/5] btrfs: abort transaction on errors in btrfs_free_chunk() David Sterba
2024-06-19 17:09 ` [PATCH 4/5] btrfs: qgroup: preallocate memory before adding a relation David Sterba
2024-06-20 1:59 ` Qu Wenruo
2024-06-20 17:40 ` David Sterba
2024-06-20 17:46 ` [PATCH v2] " David Sterba
2024-06-20 22:22 ` Qu Wenruo
2024-06-19 17:09 ` [PATCH 5/5] btrfs: qgroup: warn about inconsistent qgroups when relation update fails David Sterba
2024-06-20 21:28 ` Boris Burkov
2024-06-20 22:34 ` Qu Wenruo
2024-06-19 23:21 ` [PATCH 0/5] Error handling fixes Qu Wenruo
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.1718816796.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.