From: Nikolay Borisov <nborisov@suse.com>
To: Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] btrfs: fix error handling in commit_fs_roots
Date: Tue, 1 Dec 2020 20:08:42 +0200 [thread overview]
Message-ID: <f44de670-a5ce-334f-cf8d-a188c08e5ebf@suse.com> (raw)
In-Reply-To: <29f468ffe7b19dbebae2201f10307ec4f34f1c88.1606834393.git.josef@toxicpanda.com>
On 1.12.20 г. 16:53 ч., Josef Bacik wrote:
> While doing error injection I would sometimes get a corrupt file system.
> This is because I was injecting errors at btrfs_search_slot, but would
> only do it one time per stack. This uncovered a problem in
> commit_fs_roots, where if we get an error we would just break. However
> we're in a second loop, the first loop being a loop to find all the
nit: s/second/nested as initially I go confused about us being in a 2nd
loop iteration. Using nested makes it a bit clearer
> dirty fs roots, and then subsequent root updates would succeed clearing
> the error value.
>
> This isn't likely to happen in real scenarios, however we could
> potentially get a random ENOMEM once and then not again, and we'd end up
> with a corrupted file system. Fix this by moving the error checking
> around a bit to the main loop, as this is the only place where something
> will fail, and return the error as soon as it occurs.
>
> With this patch my reproducer no longer corrupts the file system.
>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> ---
> fs/btrfs/transaction.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c
> index 1dac76b7ea96..b05f75654b16 100644
> --- a/fs/btrfs/transaction.c
> +++ b/fs/btrfs/transaction.c
> @@ -1328,7 +1328,6 @@ static noinline int commit_fs_roots(struct btrfs_trans_handle *trans)
> struct btrfs_root *gang[8];
> int i;
> int ret;
> - int err = 0;
>
> spin_lock(&fs_info->fs_roots_radix_lock);
> while (1) {
> @@ -1340,6 +1339,8 @@ static noinline int commit_fs_roots(struct btrfs_trans_handle *trans)
> break;
> for (i = 0; i < ret; i++) {
> struct btrfs_root *root = gang[i];
> + int err;
> +
> radix_tree_tag_clear(&fs_info->fs_roots_radix,
> (unsigned long)root->root_key.objectid,
> BTRFS_ROOT_TRANS_TAG);
> @@ -1366,14 +1367,14 @@ static noinline int commit_fs_roots(struct btrfs_trans_handle *trans)
> err = btrfs_update_root(trans, fs_info->tree_root,
> &root->root_key,
> &root->root_item);
> - spin_lock(&fs_info->fs_roots_radix_lock);
> if (err)
> - break;
> + return err;
> + spin_lock(&fs_info->fs_roots_radix_lock);
> btrfs_qgroup_free_meta_all_pertrans(root);
> }
> }
> spin_unlock(&fs_info->fs_roots_radix_lock);
> - return err;
> + return 0;
> }
>
> /*
>
next prev parent reply other threads:[~2020-12-01 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 14:53 [PATCH] btrfs: fix error handling in commit_fs_roots Josef Bacik
2020-12-01 18:08 ` Nikolay Borisov [this message]
2020-12-04 16:52 ` David Sterba
2020-12-04 19:52 ` Josef Bacik
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=f44de670-a5ce-334f-cf8d-a188c08e5ebf@suse.com \
--to=nborisov@suse.com \
--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