linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Bob Copeland <me@bobcopeland.com>,
	jirislaby@gmail.com, mickflemm@gmail.com, lrodriguez@atheros.com,
	wireless <linux-wireless@vger.kernel.org>,
	John Linville <linville@tuxdriver.com>
Subject: Re: Ath5k/mac80211 triggers WARN_ON in kernel/softirq.c
Date: Thu, 30 Jul 2009 17:52:23 +0200	[thread overview]
Message-ID: <200907301752.23855.mb@bu3sch.de> (raw)
In-Reply-To: <1248968229.16129.9.camel@johannes.local>

On Thursday 30 July 2009 17:37:09 Johannes Berg wrote:
> On Thu, 2009-07-30 at 10:45 -0400, Bob Copeland wrote:
> > On Thu, Jul 30, 2009 at 10:31 AM, Michael Buesch<mb@bu3sch.de> wrote:
> > > Ath5k from today's compat-wireless triggers the following WARNing
> > > on hostapd startup.
> > > [ 1669.799870] ------------[ cut here ]------------
> > > [ 1669.799934] WARNING: at kernel/softirq.c:141 local_bh_enable_ip+0x8b/0xb0()
> > 
> > because ath5k calls ieee80211_beacon_get inside a spin_lock_irqsave()
> > and this is WARN_ON_ONCE(in_irq() || irqs_disabled).
> 
> > > [ 1669.800493]  [<ffffffff807e0fef>] _spin_unlock_bh+0xf/0x20
> > > [ 1669.800564]  [<ffffffffa0040b92>] ieee80211_beacon_get+0x2c2/0x2d0 [mac80211]
> > 
> > I guess this is the first victim of spin_lock_bh conversion?
> 
> Indeed. I think this means we need to convert the local->sta_lock back
> to _irqsave/restore.
> 
> John, can you revert the BH patch ("mac80211: do not use irq locks where
> not necessary") and I'll send a new one with those changes removed?

I didn't look at the code, but can't we simply request the beacon from
mac80211 before locking? Or isn't the spin_lock_irqsave() done in the driver?

-- 
Greetings, Michael.

  reply	other threads:[~2009-07-30 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 14:31 Ath5k/mac80211 triggers WARN_ON in kernel/softirq.c Michael Buesch
2009-07-30 14:45 ` Bob Copeland
2009-07-30 15:37   ` Johannes Berg
2009-07-30 15:52     ` Michael Buesch [this message]
2009-07-30 16:08       ` Bob Copeland
2009-08-04 14:55     ` John W. Linville
2009-07-31 22:46   ` Philip A. Prindeville
2009-08-06  1:58     ` Philip A. Prindeville

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=200907301752.23855.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=jirislaby@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@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).