Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: 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 09:49:21 +0200	[thread overview]
Message-ID: <1212047361.16917.6.camel@johannes.berg> (raw)
In-Reply-To: <200805290937.22146.hs4233@mail.mn-solutions.de> (sfid-20080529_093731_142217_77BB66EC)

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

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.

johannes

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

  reply	other threads:[~2008-05-29  7:50 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 [this message]
2008-05-29  8:05   ` Holger Schurig
2008-05-29  8:07     ` Johannes Berg
2008-05-29  8:07   ` Tomas Winkler
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=1212047361.16917.6.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=hs4233@mail.mn-solutions.de \
    --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