linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: <fdmanana@gmail.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: RE: [PATCH 3/3] btrfs: Remove BUG_ON() when failed searching block_group_cache in unpin_extent_range()
Date: Wed, 25 Feb 2015 09:18:46 +0800	[thread overview]
Message-ID: <007f01d05099$01bc2430$05346c90$@cn.fujitsu.com> (raw)
In-Reply-To: <CAL3q7H63LBgPvVcggR+fZ3KrfLWH8D7ZJDjUo_orqbrmTVmeNw@mail.gmail.com>

Hi, Filipe

> From: Filipe David Manana [mailto:fdmanana@gmail.com]
> 
> On Tue, Feb 24, 2015 at 3:37 PM, Zhaolei <zhaolei@cn.fujitsu.com> wrote:
> > From: Zhao Lei <zhaolei@cn.fujitsu.com>
> >
> > Above BUG_ON() was triggered only one time in my test, but hadn't
> > happened again in same env.
> >
> > The reason maybe:
> > A block group which include pinned space was removed before
> > unpin_extent_range(), and no other block_group_cache after "start"
> > pos, so the code entered into above BUG_ON().
> >
> > To support auto-remove-bgs, we can remove above BUG_ON(), and bypass
> > removed bgs.
> 
> I don't think it's a good idea to remove this BUG_ON().
> You're just hiding (potentially dangerous) logical bugs doing that - we need to
> understand exactly why that happens and fix it.
> 
> I fixed a scenario where this happens recently, and the fix is in 4.0-rc1:
> 
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d4b4
> 50cd4b33ce7c572e7fdccf33b59c4cdf361c
> 
> Were you testing with or without this fix?
> 
Thanks for notice, it is better way of fix.
I'll drop this patch.

Thanks
Zhaolei

> Thanks
> 
> >
> > Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
> > ---
> >  fs/btrfs/extent-tree.c | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c index
> > 8b51eb5..ef0b40d 100644
> > --- a/fs/btrfs/extent-tree.c
> > +++ b/fs/btrfs/extent-tree.c
> > @@ -5751,7 +5751,8 @@ static int unpin_extent_range(struct btrfs_root
> *root, u64 start, u64 end,
> >                         if (cache)
> >                                 btrfs_put_block_group(cache);
> >                         cache = btrfs_lookup_block_group(fs_info,
> start);
> > -                       BUG_ON(!cache); /* Logic error */
> > +                       if (!cache)
> > +                               break;
> >                 }
> >
> >                 len = cache->key.objectid + cache->key.offset - start;
> > --
> > 1.8.5.1
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
> > in the body of a message to majordomo@vger.kernel.org More majordomo
> > info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> 
> --
> Filipe David Manana,
> 
> "Reasonable men adapt themselves to the world.
>  Unreasonable men adapt the world to themselves.
>  That's why all progress depends on unreasonable men."



  reply	other threads:[~2015-02-25  1:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 15:37 [PATCH 3/3] btrfs: Remove BUG_ON() when failed searching block_group_cache in unpin_extent_range() Zhaolei
2015-02-24 16:01 ` Filipe David Manana
2015-02-25  1:18   ` Zhao Lei [this message]
2015-02-26  9:55     ` Filipe David Manana
2015-02-26 12:03       ` Zhao Lei

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='007f01d05099$01bc2430$05346c90$@cn.fujitsu.com' \
    --to=zhaolei@cn.fujitsu.com \
    --cc=fdmanana@gmail.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).