From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/5] Fixes and tweaks around error handling
Date: Wed, 16 Dec 2020 11:18:42 -0500 [thread overview]
Message-ID: <cover.1608135381.git.josef@toxicpanda.com> (raw)
Hello,
These patches were originally in my reloc error handling patches that have been
broken out on their own. They stand on their own and are simple and don't
affect the code in a real way. Simply fixing some cosmetic stuff, or allowing
error injection in certain places. They were patches I needed while running
error injection. Thanks,
Josef
Josef Bacik (5):
btrfs: allow error injection for btrfs_search_slot and btrfs_cow_block
btrfs: print the actual offset in btrfs_root_name
btrfs: noinline btrfs_should_cancel_balance
btrfs: pass down the tree block level through ref-verify
btrfs: make sure owner is set in ref-verify
fs/btrfs/ctree.c | 2 ++
fs/btrfs/disk-io.c | 2 +-
fs/btrfs/print-tree.c | 10 +++++-----
fs/btrfs/print-tree.h | 2 +-
fs/btrfs/ref-verify.c | 43 ++++++++++++++++++++++---------------------
fs/btrfs/relocation.c | 2 +-
6 files changed, 32 insertions(+), 29 deletions(-)
--
2.26.2
next reply other threads:[~2020-12-16 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 16:18 Josef Bacik [this message]
2020-12-16 16:18 ` [PATCH 1/5] btrfs: allow error injection for btrfs_search_slot and btrfs_cow_block Josef Bacik
2020-12-16 16:18 ` [PATCH 2/5] btrfs: print the actual offset in btrfs_root_name Josef Bacik
2020-12-18 15:22 ` David Sterba
2020-12-16 16:18 ` [PATCH 3/5] btrfs: noinline btrfs_should_cancel_balance Josef Bacik
2020-12-16 16:18 ` [PATCH 4/5] btrfs: pass down the tree block level through ref-verify Josef Bacik
2020-12-16 16:18 ` [PATCH 5/5] btrfs: make sure owner is set in ref-verify Josef Bacik
2020-12-17 12:56 ` [PATCH 0/5] Fixes and tweaks around error handling Nikolay Borisov
2020-12-18 15:38 ` 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.1608135381.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=kernel-team@fb.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