Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Opencode ordered_data_tree_panic
Date: Fri, 29 Nov 2019 15:18:22 +0100	[thread overview]
Message-ID: <20191129141822.GL2734@twin.jikos.cz> (raw)
In-Reply-To: <d310c88f-547a-a5db-09a7-74d8a22957c1@suse.com>

On Fri, Nov 29, 2019 at 11:49:23AM +0200, Nikolay Borisov wrote:
> 
> 
> On 29.11.19 г. 11:38 ч., Nikolay Borisov wrote:
> > It's a simple wrapper over btrfs_panic and is called only once. Just
> > open code it.
> > 
> > Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> > ---
> >  fs/btrfs/extent-tree.c  |  5 +----
> >  fs/btrfs/ordered-data.c | 10 +---------
> >  2 files changed, 2 insertions(+), 13 deletions(-)
> > 
> > diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> > index f68b38f44f0b..ab99ec6e188b 100644
> > --- a/fs/btrfs/extent-tree.c
> > +++ b/fs/btrfs/extent-tree.c
> > @@ -4172,11 +4172,8 @@ int btrfs_free_reserved_extent(struct btrfs_fs_info *fs_info,
> >  	struct btrfs_block_group *cache;
> >  
> >  	cache = btrfs_lookup_block_group(fs_info, start);
> > -	if (!cache) {
> > -		btrfs_err(fs_info, "Unable to find block group for %llu",
> > -			  start);
> > +	if (!cache)
> >  		return -ENOSPC;
> > -	}
> >  
> >  	btrfs_add_free_space(cache, start, len);
> >  	btrfs_free_reserved_bytes(cache, len, delalloc);
> 
> Grrr this hunk should be dropped.... Shall I resend ?

No, i'll drop it

  reply	other threads:[~2019-11-29 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29  9:38 [PATCH] btrfs: Opencode ordered_data_tree_panic Nikolay Borisov
2019-11-29  9:49 ` Nikolay Borisov
2019-11-29 14:18   ` David Sterba [this message]
2019-12-03 19:25 ` 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=20191129141822.GL2734@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    /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