linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Steve French <smfrench@gmail.com>,
	Stalin Kenny <stalinlinux@gmail.com>,
	linux-sparse@vger.kernel.org
Subject: Re: context imbalance false positive sparse warnings
Date: Wed, 10 Sep 2008 09:47:11 +0200	[thread overview]
Message-ID: <1221032831.12266.8.camel@johannes.berg> (raw)
In-Reply-To: <1219184769.17033.95.camel@brick> (sfid-20080820_002610_629541_77E70AA8)

[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]

On Tue, 2008-08-19 at 15:26 -0700, Harvey Harrison wrote:
> On Tue, 2008-08-19 at 17:22 -0500, Steve French wrote:
> > On Tue, Aug 19, 2008 at 5:00 PM, Stalin Kenny <stalinlinux@gmail.com> wrote:
> > >> Even the simplest use cases throw this error e.g. fs/super.c line 162-164:
> > >>
> > >> static void put_super(struct super_block *sb)
> > >> {
> > >>       spin_lock(&sb_lock);
> > >>       __put_super(sb);
> > >>       spin_unlock(&sb_lock);
> > >> }
> > >
> > > What is the sparse error when you call this function ?
> > CHECK   fs/super.c
> > fs/super.c:164:2: warning: context imbalance in 'put_super': wrong count at exit
> > fs/super.c:164:2:    context 'lock': wanted 0, got 1
> > 
> > 
> 
> Johannes Berg had a 9-patch series that improved this somewhat, but they had
> some bugs in them (crashes).  But I've been running with them anyway as they
> do improve cases like this significantly.

I've just sent out a fixed version and with it I get no errors on
fs/super.c when I apply this small fixup:

diff --git a/fs/super.c b/fs/super.c
index e931ae9..6810845 100644
--- a/fs/super.c
+++ b/fs/super.c
@@ -201,7 +201,7 @@ EXPORT_SYMBOL(deactivate_super);
  *	success, 0 if we had failed (superblock contents was already dead or
  *	dying when grab_super() had been called).
  */
-static int grab_super(struct super_block *s) __releases(sb_lock)
+static int grab_super(struct super_block *s) __releases(&sb_lock)
 {
 	s->s_count++;
 	spin_unlock(&sb_lock);

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2008-09-10  7:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 21:47 context imbalance false positive sparse warnings Steve French
2008-08-19 22:00 ` Stalin Kenny
2008-08-19 22:22   ` Steve French
2008-08-19 22:26     ` Harvey Harrison
2008-09-10  7:47       ` Johannes Berg [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=1221032831.12266.8.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --cc=stalinlinux@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).