linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: remove warnings superseded by refcount_t usage
Date: Tue, 26 Jun 2018 17:00:46 +0300	[thread overview]
Message-ID: <fae25e89-52c5-25ea-65ad-7405fedb0a68@suse.com> (raw)
In-Reply-To: <20180625163822.25681-1-dsterba@suse.com>



On 25.06.2018 19:38, David Sterba wrote:
> There are several WARN_ON calls that catch incrorrect reference counter
> updates, but this is what the refcount_t does already:
> 
> * refcount_inc from 0 will warn
> * refcount_dec_and_test from 0 will warn
> 

But these warnings are only going to be triggered in the case of
CONFIG_REFCOUNT_FULL otherwise refcount falls back to plain atomic
operations.

> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
>  fs/btrfs/delayed-ref.h | 1 -
>  fs/btrfs/extent_map.c  | 2 +-
>  fs/btrfs/transaction.c | 1 -
>  fs/btrfs/volumes.c     | 1 -
>  4 files changed, 1 insertion(+), 4 deletions(-)
> 
> diff --git a/fs/btrfs/delayed-ref.h b/fs/btrfs/delayed-ref.h
> index ea1aecb6a50d..16ee92c541bf 100644
> --- a/fs/btrfs/delayed-ref.h
> +++ b/fs/btrfs/delayed-ref.h
> @@ -210,7 +210,6 @@ btrfs_free_delayed_extent_op(struct btrfs_delayed_extent_op *op)
>  
>  static inline void btrfs_put_delayed_ref(struct btrfs_delayed_ref_node *ref)
>  {
> -	WARN_ON(refcount_read(&ref->refs) == 0);
>  	if (refcount_dec_and_test(&ref->refs)) {
>  		WARN_ON(ref->in_tree);
>  		switch (ref->type) {
> diff --git a/fs/btrfs/extent_map.c b/fs/btrfs/extent_map.c
> index 6648d55e5339..6808ad4ed3c9 100644
> --- a/fs/btrfs/extent_map.c
> +++ b/fs/btrfs/extent_map.c
> @@ -72,7 +72,7 @@ void free_extent_map(struct extent_map *em)
>  {
>  	if (!em)
>  		return;
> -	WARN_ON(refcount_read(&em->refs) == 0);
> +
>  	if (refcount_dec_and_test(&em->refs)) {
>  		WARN_ON(extent_map_in_tree(em));
>  		WARN_ON(!list_empty(&em->list));
> diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c
> index 4485eae41e88..f6b68099b767 100644
> --- a/fs/btrfs/transaction.c
> +++ b/fs/btrfs/transaction.c
> @@ -41,7 +41,6 @@ static const unsigned int btrfs_blocked_trans_types[TRANS_STATE_MAX] = {
>  
>  void btrfs_put_transaction(struct btrfs_transaction *transaction)
>  {
> -	WARN_ON(refcount_read(&transaction->use_count) == 0);
>  	if (refcount_dec_and_test(&transaction->use_count)) {
>  		BUG_ON(!list_empty(&transaction->list));
>  		WARN_ON(!RB_EMPTY_ROOT(&transaction->delayed_refs.href_root));
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index e034ad9e23b4..f64d26b4f278 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -5330,7 +5330,6 @@ static struct btrfs_bio *alloc_btrfs_bio(int total_stripes, int real_stripes)
>  
>  void btrfs_get_bbio(struct btrfs_bio *bbio)
>  {
> -	WARN_ON(!refcount_read(&bbio->refs));
>  	refcount_inc(&bbio->refs);
>  }
>  
> 

  reply	other threads:[~2018-06-26 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 16:38 [PATCH] btrfs: remove warnings superseded by refcount_t usage David Sterba
2018-06-26 14:00 ` Nikolay Borisov [this message]
2018-06-29 14:05   ` David Sterba
2018-07-05 15:55     ` 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=fae25e89-52c5-25ea-65ad-7405fedb0a68@suse.com \
    --to=nborisov@suse.com \
    --cc=dsterba@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;
as well as URLs for NNTP newsgroup(s).