From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: [PATCH 05/12] btrfs: remove useless mutex lock/unlock sequences
Date: Fri, 22 Apr 2011 11:41:51 +0200 [thread overview]
Message-ID: <b5fefb09811c22cd101a44ac753293af942087fc.1303398927.git.dsterba@suse.cz> (raw)
In-Reply-To: <cover.1303398927.git.dsterba@suse.cz>
Signed-off-by: David Sterba <dsterba@suse.cz>
---
fs/btrfs/extent-tree.c | 6 ------
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index 31f33ba..c97ceab 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -756,8 +756,6 @@ again:
btrfs_release_path(root->fs_info->extent_root, path);
- mutex_lock(&head->mutex);
- mutex_unlock(&head->mutex);
btrfs_put_delayed_ref(&head->node);
goto again;
}
@@ -2297,8 +2295,6 @@ again:
atomic_inc(&ref->refs);
spin_unlock(&delayed_refs->lock);
- mutex_lock(&head->mutex);
- mutex_unlock(&head->mutex);
btrfs_put_delayed_ref(ref);
cond_resched();
@@ -2363,8 +2359,6 @@ static noinline int check_delayed_ref(struct btrfs_trans_handle *trans,
btrfs_release_path(root->fs_info->extent_root, path);
- mutex_lock(&head->mutex);
- mutex_unlock(&head->mutex);
btrfs_put_delayed_ref(&head->node);
return -EAGAIN;
}
--
1.7.5.rc3
next prev parent reply other threads:[~2011-04-22 9:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 9:41 [PATCH 00/12] Cleanups, cruft removal David Sterba
2011-04-22 9:41 ` [PATCH 01/12] btrfs: rename variables clashing with global function names David Sterba
2011-04-22 9:41 ` [PATCH 02/12] btrfs: remove nested duplicate variable declarations David Sterba
2011-04-22 9:41 ` [PATCH 03/12] btrfs: fix dereference before check David Sterba
2011-04-22 9:41 ` [PATCH 04/12] btrfs: unify checking of IS_ERR and null David Sterba
2011-04-22 9:41 ` David Sterba [this message]
2011-04-25 6:25 ` [PATCH 05/12] btrfs: remove useless mutex lock/unlock sequences Tsutomu Itoh
2011-04-25 12:12 ` Chris Mason
2011-04-29 16:34 ` David Sterba
2011-05-02 13:49 ` [PATCH] btrfs: Document a mutex lock/unlock sequence David Sterba
2011-04-22 9:41 ` [PATCH 06/12] btrfs: make functions static when possible David Sterba
2011-04-22 9:42 ` [PATCH 07/12] btrfs: drop unused argument from extent_io_tree_init David Sterba
2011-04-22 9:42 ` [PATCH 08/12] btrfs: drop unused parameter from extent_map_tree_init David Sterba
2011-04-22 9:42 ` [PATCH 09/12] btrfs: drop gfp parameter from alloc_extent_map David Sterba
2011-04-22 9:42 ` [PATCH 10/12] btrfs: drop gfp parameter from find_extent_buffer David Sterba
2011-04-22 9:43 ` [PATCH 11/12] btrfs: drop gfp parameter from alloc_extent_buffer David Sterba
2011-04-22 9:43 ` [PATCH 12/12] btrfs: drop unused parameter from btrfs_release_path David Sterba
2011-05-02 14:01 ` [PATCH 00/12] Cleanups, cruft removal 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=b5fefb09811c22cd101a44ac753293af942087fc.1303398927.git.dsterba@suse.cz \
--to=dsterba@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.