linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: linux-btrfs@vger.kernel.org, Slava Barinov <rayslava@gmail.com>,
	David Sterba <dsterba@suse.cz>
Subject: Re: [PATCH] Btrfs: reset path lock state to zero
Date: Sat, 29 Dec 2012 23:06:33 +0800	[thread overview]
Message-ID: <20121229150632.GA7874@liubo> (raw)
In-Reply-To: <CAKcLGm_jZuzHwA=MBxakLPz+hwoDeFd0TXjg_TtbEvWB+jkfwA@mail.gmail.com>

On Fri, Dec 28, 2012 at 12:32:25PM -0600, Mitch Harder wrote:
> On Fri, Dec 28, 2012 at 3:33 AM, Liu Bo <bo.li.liu@oracle.com> wrote:
> > We forgot to reset the path lock state to zero after we unlock the path block,
> > and this can lead to the ASSERT checker in tree unlock API.
> >
> > Reported-by: Slava Barinov <rayslava@gmail.com>
> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> > ---
> >  fs/btrfs/extent-tree.c |    2 ++
> >  1 files changed, 2 insertions(+), 0 deletions(-)
> >
> > diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> > index 521e9d4..a71d457 100644
> > --- a/fs/btrfs/extent-tree.c
> > +++ b/fs/btrfs/extent-tree.c
> > @@ -6788,11 +6788,13 @@ static noinline int walk_up_proc(struct btrfs_trans_handle *trans,
> >                                                        &wc->flags[level]);
> >                         if (ret < 0) {
> >                                 btrfs_tree_unlock_rw(eb, path->locks[level]);
> > +                               path->locks[level] = 0;
> >                                 return ret;
> >                         }
> >                         BUG_ON(wc->refs[level] == 0);
> >                         if (wc->refs[level] == 1) {
> >                                 btrfs_tree_unlock_rw(eb, path->locks[level]);
> > +                               path->locks[level] = 0;
> >                                 return 1;
> >                         }
> >                 }
> > --
> > 1.7.7.6
> >
> > --
> > 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
> 
> This patch seems to clear a lock WARNING I've been seeing recently.
> 
> http://permalink.gmane.org/gmane.comp.file-systems.btrfs/21692
> 
> I'm unable to generate the WARNING after applying this patch.

Good, they are related judging from your stack info :)

thanks,
liubo
> 
> Thanks.

      reply	other threads:[~2012-12-29 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28  9:33 [PATCH] Btrfs: reset path lock state to zero Liu Bo
2012-12-28 18:32 ` Mitch Harder
2012-12-29 15:06   ` Liu Bo [this message]

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=20121229150632.GA7874@liubo \
    --to=bo.li.liu@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mitch.harder@sabayonlinux.org \
    --cc=rayslava@gmail.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;
as well as URLs for NNTP newsgroup(s).