From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Christopher Li" <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: sparse: possible false report of context imbalance
Date: Wed, 16 Oct 2013 22:23:56 -0500 [thread overview]
Message-ID: <525F584C.5010106@lwfinger.net> (raw)
Hi,
Sparse reports the following:
CHECK drivers/staging/rtl8188eu/core/rtw_mlme.c
drivers/staging/rtl8188eu/core/rtw_mlme.c:1003:9: warning: context imbalance in
'rtw_free_assoc_resources' - different lock contexts for basic block
The code in question is as follows:
if (lock_scanned_queue)
spin_lock_bh(&(pmlmepriv->scanned_queue.lock));
pwlan = rtw_find_network(&pmlmepriv->scanned_queue,
tgt_network->network.MacAddress);
if (lock_scanned_queue)
spin_unlock_bh(&(pmlmepriv->scanned_queue.lock));
As this fragment uses the identical test to unlock that is used to lock, and the
test variable is not touched, I think this is a false indication. I am using
version 0.4.4 of sparse.
Thanks,
Larry
next reply other threads:[~2013-10-17 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 3:23 Larry Finger [this message]
2013-10-17 16:25 ` sparse: possible false report of context imbalance Josh Triplett
2013-10-17 17:41 ` Larry Finger
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=525F584C.5010106@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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