From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: dsterba@suse.cz, kernel-team@fb.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 5/7] btrfs: clear BTRFS_ROOT_DEAD_RELOC_TREE before dropping the reloc root
Date: Tue, 3 Mar 2020 16:34:31 +0100 [thread overview]
Message-ID: <20200303153431.GF2902@twin.jikos.cz> (raw)
In-Reply-To: <ab3e1533-d0e3-8ab7-0d72-acf71ce66968@toxicpanda.com>
On Mon, Mar 02, 2020 at 02:51:11PM -0500, Josef Bacik wrote:
> On 3/2/20 2:31 PM, David Sterba wrote:
> > On Mon, Mar 02, 2020 at 01:47:55PM -0500, Josef Bacik wrote:
> >> We were doing the clear dance for the reloc root after doing the drop of
> >> the reloc root, which means we have a giant window where we could miss
> >> having BTRFS_ROOT_DEAD_RELOC_TREE unset and the reloc_root == NULL.
> >>
> >> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> >> ---
> >> fs/btrfs/relocation.c | 13 +++++++------
> >> 1 file changed, 7 insertions(+), 6 deletions(-)
> >>
> >> diff --git a/fs/btrfs/relocation.c b/fs/btrfs/relocation.c
> >> index e60450c44406..acd21c156378 100644
> >> --- a/fs/btrfs/relocation.c
> >> +++ b/fs/btrfs/relocation.c
> >> @@ -2291,18 +2291,19 @@ static int clean_dirty_subvols(struct reloc_control *rc)
> >>
> >> list_del_init(&root->reloc_dirty_list);
> >> root->reloc_root = NULL;
> >> - if (reloc_root) {
> >> -
> >> - ret2 = btrfs_drop_snapshot(reloc_root, NULL, 0, 1);
> >> - if (ret2 < 0 && !ret)
> >> - ret = ret2;
> >> - }
> >> /*
> >> * Need barrier to ensure clear_bit() only happens after
> >> * root->reloc_root = NULL. Pairs with have_reloc_root.
> >> */
> >> smp_wmb();
> >> clear_bit(BTRFS_ROOT_DEAD_RELOC_TREE, &root->state);
> >> +
> >> + if (reloc_root) {
> >> +
> >> + ret2 = btrfs_drop_snapshot(reloc_root, NULL, 0, 1);
> >> + if (ret2 < 0 && !ret)
> >> + ret = ret2;
> >> + }
> >
> > This reverts fix 1fac4a54374f7ef385938f3c6cf7649c0fe4f6cd that moved if
> > (reloc_root) before the clear_bit.
> >
>
> Hmm we should probably keep this and move the
>
> if (root->reloc_root)
>
> thing after the
>
> if (!rc || !rc->create_reloc_tree ||
> root->root_key.objectid == BTRFS_TREE_RELOC_OBJECTID)
> return 0;
>
> to properly fix this. I'll add this and send an updated series. Thanks,
Also please update the changelog, it's too vague for a code that had
several bugs regarding the reloc_root lifetime.
next prev parent reply other threads:[~2020-03-03 15:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 18:47 [PATCH 0/7] relocation error handling fixes Josef Bacik
2020-03-02 18:47 ` [PATCH 1/7] btrfs: drop block from cache on error in relocation Josef Bacik
2020-03-03 0:59 ` Qu Wenruo
2020-03-03 14:59 ` David Sterba
2020-03-03 20:27 ` Josef Bacik
2020-03-02 18:47 ` [PATCH 2/7] btrfs: unset reloc control if we fail to recover Josef Bacik
2020-03-03 0:58 ` Qu Wenruo
2020-03-03 1:03 ` Josef Bacik
2020-03-03 1:18 ` Qu Wenruo
2020-03-03 15:21 ` David Sterba
2020-03-02 18:47 ` [PATCH 3/7] btrfs: splice rc->reloc_roots onto reloc roots in recover Josef Bacik
2020-03-03 1:02 ` Qu Wenruo
2020-03-02 18:47 ` [PATCH 4/7] btrfs: run clean_dirty_subvols if we fail to start a trans Josef Bacik
2020-03-03 1:04 ` Qu Wenruo
2020-03-03 15:32 ` David Sterba
2020-03-02 18:47 ` [PATCH 5/7] btrfs: clear BTRFS_ROOT_DEAD_RELOC_TREE before dropping the reloc root Josef Bacik
2020-03-02 19:31 ` David Sterba
2020-03-02 19:51 ` Josef Bacik
2020-03-03 15:34 ` David Sterba [this message]
2020-03-03 0:31 ` Qu Wenruo
2020-03-02 18:47 ` [PATCH 6/7] btrfs: hold a ref on the root->reloc_root Josef Bacik
2020-03-03 1:12 ` Qu Wenruo
2020-03-03 1:14 ` Josef Bacik
2020-03-03 15:51 ` David Sterba
2020-03-02 18:47 ` [PATCH 7/7] btrfs: remove a BUG_ON() from merge_reloc_roots() Josef Bacik
2020-03-03 1:17 ` 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=20200303153431.GF2902@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