* [PATCH] Btrfs: remove ourselves from the cluster list under lock
@ 2013-08-22 21:04 Josef Bacik
2013-08-23 7:43 ` Miao Xie
0 siblings, 1 reply; 2+ messages in thread
From: Josef Bacik @ 2013-08-22 21:04 UTC (permalink / raw)
To: linux-btrfs
A user was reporting weird warnings from btrfs_put_delayed_ref() and I noticed
that we were doing this list_del_init() on our head ref outside of
delayed_refs->lock. This is a problem if we have people still on the list, we
could end up modifying old pointers and such. Fix this by removing us from the
list before we do our run_delayed_ref on our head ref. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
---
fs/btrfs/extent-tree.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index 4c89566..95c6539 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -2440,6 +2440,8 @@ static noinline int run_clustered_refs(struct btrfs_trans_handle *trans,
default:
WARN_ON(1);
}
+ } else {
+ list_del_init(&locked_ref->cluster);
}
spin_unlock(&delayed_refs->lock);
@@ -2462,7 +2464,6 @@ static noinline int run_clustered_refs(struct btrfs_trans_handle *trans,
* list before we release it.
*/
if (btrfs_delayed_ref_is_head(ref)) {
- list_del_init(&locked_ref->cluster);
btrfs_delayed_ref_unlock(locked_ref);
locked_ref = NULL;
}
--
1.7.7.6
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] Btrfs: remove ourselves from the cluster list under lock
2013-08-22 21:04 [PATCH] Btrfs: remove ourselves from the cluster list under lock Josef Bacik
@ 2013-08-23 7:43 ` Miao Xie
0 siblings, 0 replies; 2+ messages in thread
From: Miao Xie @ 2013-08-23 7:43 UTC (permalink / raw)
To: Josef Bacik; +Cc: linux-btrfs
On thu, 22 Aug 2013 17:04:59 -0400, Josef Bacik wrote:
> A user was reporting weird warnings from btrfs_put_delayed_ref() and I noticed
> that we were doing this list_del_init() on our head ref outside of
> delayed_refs->lock. This is a problem if we have people still on the list, we
> could end up modifying old pointers and such. Fix this by removing us from the
> list before we do our run_delayed_ref on our head ref. Thanks,
Looks good.
Reviewed-by: Miao Xie <miaox@cn.fujitsu.com>
>
> Signed-off-by: Josef Bacik <jbacik@fusionio.com>
> ---
> fs/btrfs/extent-tree.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index 4c89566..95c6539 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -2440,6 +2440,8 @@ static noinline int run_clustered_refs(struct btrfs_trans_handle *trans,
> default:
> WARN_ON(1);
> }
> + } else {
> + list_del_init(&locked_ref->cluster);
> }
> spin_unlock(&delayed_refs->lock);
>
> @@ -2462,7 +2464,6 @@ static noinline int run_clustered_refs(struct btrfs_trans_handle *trans,
> * list before we release it.
> */
> if (btrfs_delayed_ref_is_head(ref)) {
> - list_del_init(&locked_ref->cluster);
> btrfs_delayed_ref_unlock(locked_ref);
> locked_ref = NULL;
> }
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-08-23 7:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-22 21:04 [PATCH] Btrfs: remove ourselves from the cluster list under lock Josef Bacik
2013-08-23 7:43 ` Miao Xie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).