Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Holger Schurig" <hs4233@mail.mn-solutions.de>,
	"Linux Wireless" <linux-wireless@vger.kernel.org>,
	libertas-dev@lists.infradead.org
Subject: Re: question about ...: wrong count at exit"
Date: Thu, 29 May 2008 11:07:19 +0300	[thread overview]
Message-ID: <1ba2fa240805290107r2c3b68cbh4bf18e86c9f96335@mail.gmail.com> (raw)
In-Reply-To: <1212047361.16917.6.camel@johannes.berg>

On Thu, May 29, 2008 at 10:49 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Thu, 2008-05-29 at 09:37 +0200, Holger Schurig wrote:
>> After pulling the newest sparse, I got some new sparse warnings
>> which puzzle me. Here's one of them:
>>
>> drivers/net/wireless/libertas/main.c:477:9: warning: context imbalance in 'lbs_eth_stop': wrong count at exit
>> drivers/net/wireless/libertas/main.c:477:9:    context 'lock': wanted 0, got 1
>>
>> However, the function looks quite innocent, and I cannot see
>> any imbalance there. Did I oversee something or is that a
>> problem of sparse?
>
>>         spin_lock_irq(&priv->driver_lock);
>>         priv->infra_open = 0;
>>         netif_stop_queue(dev);
>>         spin_unlock_irq(&priv->driver_lock);
>
> I think it's a sparse problem caused by my patch, I sent further patches
> to fix it but they were never applied (and had a slight remaining
> problem too). If you look at the pre-processed function it should become
> obvious.
>

I got plenty of this in the mac80211 reported with newest sparse, but
they looks false caused by 'goto statements'

Tomas

  parent reply	other threads:[~2008-05-29  8:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29  7:37 question about ...: wrong count at exit" Holger Schurig
2008-05-29  7:49 ` Johannes Berg
2008-05-29  8:05   ` Holger Schurig
2008-05-29  8:07     ` Johannes Berg
2008-05-29  8:07   ` Tomas Winkler [this message]
2008-05-29  8:33     ` Johannes Berg
2008-05-29  8:37       ` Johannes Berg

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=1ba2fa240805290107r2c3b68cbh4bf18e86c9f96335@mail.gmail.com \
    --to=tomasw@gmail.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=johannes@sipsolutions.net \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.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