From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 0/5] Fixes and tweaks around error handling
Date: Fri, 18 Dec 2020 16:38:35 +0100 [thread overview]
Message-ID: <20201218153835.GA6430@twin.jikos.cz> (raw)
In-Reply-To: <cover.1608135381.git.josef@toxicpanda.com>
On Wed, Dec 16, 2020 at 11:18:42AM -0500, Josef Bacik wrote:
> 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
Added to misc-next, with some changelog adjustments, thanks.
prev parent reply other threads:[~2020-12-18 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 16:18 [PATCH 0/5] Fixes and tweaks around error handling Josef Bacik
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 [this message]
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=20201218153835.GA6430@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=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