From: Liu Bo <bo.li.liu@oracle.com>
To: Slava Barinov <rayslava@gmail.com>
Cc: David Sterba <dsterba@suse.cz>, linux-btrfs@vger.kernel.org
Subject: Re: BUG at fs/btrfs/locking.c:265
Date: Fri, 28 Dec 2012 17:49:07 +0800 [thread overview]
Message-ID: <20121228094906.GA7283@liubo> (raw)
In-Reply-To: <20121227132437.GS14116@twin.jikos.cz>
Hi Slava, David,
I've sent a patch to fix the bug(Cced you), could you please check if it
works? :)
thanks,
liubo
On Thu, Dec 27, 2012 at 02:24:37PM +0100, David Sterba wrote:
> On Thu, Dec 27, 2012 at 04:07:31PM +0800, Liu Bo wrote:
> > On Thu, Dec 27, 2012 at 08:27:11AM +0400, Slava Barinov wrote:
> > > And there's nothing in dmesg that could help user to understand what
> > > happened. I've lost about ten minutes trying to understand what does
> > > it want from me.
> >Could you please show me what line does 'walk_down_proc+0x2b0/0x2e0 [btrfs]'
> > refer to?
>
> It's
>
> 6578 if (path->locks[level] && level > 0) {
> 6579 btrfs_tree_unlock_rw(eb, path->locks[level]);
> ^^^^
> 6580 path->locks[level] = 0;
> 6581 }
> 6582 return 0;
>
> which calls btrfs_tree_unlock() and hits the
>
> 241 void btrfs_tree_unlock(struct extent_buffer *eb)
> 242 {
> 243 int blockers = atomic_read(&eb->blocking_writers);
> 244
> 245 BUG_ON(blockers > 1);
> 246
> 247 btrfs_assert_tree_locked(eb);
>
> ->
>
> 263 void btrfs_assert_tree_locked(struct extent_buffer *eb)
> 264 {
> 265 BUG_ON(!atomic_read(&eb->write_locks));
> 266 }
>
>
> david
prev parent reply other threads:[~2012-12-28 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 4:27 BUG at fs/btrfs/locking.c:265 Slava Barinov
2012-12-27 8:07 ` Liu Bo
2012-12-27 13:24 ` David Sterba
2012-12-28 9:49 ` 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=20121228094906.GA7283@liubo \
--to=bo.li.liu@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.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