From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 1/2] btrfs: Remove superflous lock acquisition in __del_reloc_root
Date: Fri, 21 Feb 2020 15:11:23 +0200 [thread overview]
Message-ID: <20200221131124.24105-1-nborisov@suse.com> (raw)
__del_reloc_root is called from:
a) Transaction commit via:
btrfs_transaction_commit
commit_fs_roots
btrfs_update_reloc_root
__del_reloc_root
b) From the relocation thread with the following call chains:
relocate_block_group
merge_reloc_roots
insert_dirty_subvol
btrfs_update_reloc_root
__del_reloc_root
c) merge_reloc_roots
free_reloc_roots
__del_reloc_roots
(The above call chain can called from btrfs_recover_relocation as well
but for the purpose of this fix this is irrelevant).
The commont data structure that needs protecting is
fs_info->reloc_ctl->reloc_list as reloc roots are anchored at this list.
Turns out it's no needed to hold the trans_lock in __del_reloc_root
since consistency is already guaranteed by call chain b) above holding
a transaction while calling insert_dirty_subvol, meaning we cannot have
a concurrent transaction commit. For call chain c) above a snapshot of
the fs_info->reloc_ctl->reloc_list is taken with reloc_mutex held and
free_reloc_roots is called on this local snapshot.
Those invariants are sufficient to prevent racing calls to
__del_reloc_root alongside other users of the list, as such it's fine
to drop the lock acquisition.
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
---
fs/btrfs/relocation.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/btrfs/relocation.c b/fs/btrfs/relocation.c
index 8076c340749f..e5cb64409f7c 100644
--- a/fs/btrfs/relocation.c
+++ b/fs/btrfs/relocation.c
@@ -1381,9 +1381,7 @@ static void __del_reloc_root(struct btrfs_root *root)
BUG_ON((struct btrfs_root *)node->data != root);
}
- spin_lock(&fs_info->trans_lock);
list_del_init(&root->root_list);
- spin_unlock(&fs_info->trans_lock);
kfree(node);
}
--
2.17.1
next reply other threads:[~2020-02-21 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 13:11 Nikolay Borisov [this message]
2020-02-21 13:11 ` [PATCH 2/2] btrfs: Use list_for_each_entry_safe in free_reloc_roots Nikolay Borisov
2020-02-21 13:17 ` [PATCH v2 " Nikolay Borisov
2020-02-21 13:23 ` [PATCH " Qu Wenruo
2020-04-10 16:33 ` David Sterba
2020-02-21 13:22 ` [PATCH 1/2] btrfs: Remove superflous lock acquisition in __del_reloc_root Qu Wenruo
2020-04-10 16:29 ` 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=20200221131124.24105-1-nborisov@suse.com \
--to=nborisov@suse.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