From: David Sterba <dsterba@suse.cz>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: nick <yocto6@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Sparse Warnings about locks in extent-tree.c
Date: Tue, 23 Sep 2014 16:01:41 +0200 [thread overview]
Message-ID: <20140923140141.GU9715@twin.jikos.cz> (raw)
In-Reply-To: <20140923064543.GA3337@localhost.localdomain>
On Tue, Sep 23, 2014 at 02:45:44PM +0800, Liu Bo wrote:
> On Mon, Sep 22, 2014 at 09:57:35PM -0400, nick wrote:
> > Hello Btfs Developers,
> > I am new so am unsure of how to fix this but we are hitting some sparse warnings about unlock/lock is having
> > a wrong count when exiting certain functions in extent-tree.c. I will paste the warnings below for you guys.
> > Hope this is of help.
> > Cheers,
> > Nick
> > fs/btrfs/extent-tree.c:6386:39: warning: context imbalance in 'btrfs_lock_cluster' - wrong count at exit
> > fs/btrfs/extent-tree.c:6663:44: warning: context imbalance in 'find_free_extent' - unexpected unlock
> > fs/btrfs/extent-tree.c:8810:9: warning: context imbalance in 'btrfs_put_block_group_cache' - wrong count at exit
>
> What program is producing these warning? It looks like a static code analysis
> tool or something.
https://sparse.wiki.kernel.org/index.php/Main_Page
It understands a few semantics like the locking and reports when there's
an unannotated function that has imbalanced locking, like the errors
above.
Any static analyzer has some ratio of false positives so not every
report means there's a bug. One would expect that a function
'btrfs_lock_cluster' would act as a lock and leaves some locks held at
exit. The "fix" is to annotate it a after review.
next prev parent reply other threads:[~2014-09-23 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 1:57 Sparse Warnings about locks in extent-tree.c nick
2014-09-23 6:45 ` Liu Bo
2014-09-23 14:01 ` David Sterba [this message]
2014-09-23 14:07 ` Liu Bo
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=20140923140141.GU9715@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=yocto6@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).