From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/8] btrfs: remove a couple BUG_ON()s and cleanups
Date: Fri, 30 Jun 2023 16:03:43 +0100 [thread overview]
Message-ID: <cover.1688137155.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
The first patch removes a couple unnecessary BUG_ON()'s, since all
callers are able to properly deal with errors, which are triggered by
syzbot with error injection (-ENOMEM). The rest are just some followup
cleanups. More details in the changelogs.
Filipe Manana (8):
btrfs: remove BUG_ON()'s in add_new_free_space()
btrfs: update documentation for add_new_free_space()
btrfs: rename add_new_free_space() to btrfs_add_new_free_space()
btrfs: make btrfs_destroy_marked_extents() return void
btrfs: make btrfs_destroy_pinned_extent() return void
btrfs: make find_first_extent_bit() return a boolean
btrfs: open code trivial btrfs_add_excluded_extent()
btrfs: move btrfs_free_excluded_extents() into block-group.c
fs/btrfs/block-group.c | 91 +++++++++++++++++++++++++------------
fs/btrfs/block-group.h | 4 +-
fs/btrfs/dev-replace.c | 6 +--
fs/btrfs/disk-io.c | 31 ++++---------
fs/btrfs/extent-io-tree.c | 14 +++---
fs/btrfs/extent-io-tree.h | 6 +--
fs/btrfs/extent-tree.c | 26 +----------
fs/btrfs/extent-tree.h | 3 --
fs/btrfs/free-space-cache.c | 7 ++-
fs/btrfs/free-space-tree.c | 27 ++++++++---
fs/btrfs/relocation.c | 10 ++--
fs/btrfs/transaction.c | 8 ++--
fs/btrfs/volumes.c | 6 +--
13 files changed, 124 insertions(+), 115 deletions(-)
--
2.34.1
next reply other threads:[~2023-06-30 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 15:03 fdmanana [this message]
2023-06-30 15:03 ` [PATCH 1/8] btrfs: remove BUG_ON()'s in add_new_free_space() fdmanana
2023-06-30 15:03 ` [PATCH 2/8] btrfs: update documentation for add_new_free_space() fdmanana
2023-06-30 15:03 ` [PATCH 3/8] btrfs: rename add_new_free_space() to btrfs_add_new_free_space() fdmanana
2023-06-30 15:03 ` [PATCH 4/8] btrfs: make btrfs_destroy_marked_extents() return void fdmanana
2023-06-30 15:03 ` [PATCH 5/8] btrfs: make btrfs_destroy_pinned_extent() " fdmanana
2023-06-30 15:03 ` [PATCH 6/8] btrfs: make find_first_extent_bit() return a boolean fdmanana
2023-06-30 15:03 ` [PATCH 7/8] btrfs: open code trivial btrfs_add_excluded_extent() fdmanana
2023-06-30 15:03 ` [PATCH 8/8] btrfs: move btrfs_free_excluded_extents() into block-group.c fdmanana
[not found] ` <20230707221740.GH2565448@zen>
2023-07-10 9:56 ` Filipe Manana
2023-07-12 16:10 ` David Sterba
2023-07-12 16:04 ` [PATCH 0/8] btrfs: remove a couple BUG_ON()s and cleanups 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.1688137155.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--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