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: Kalle Valo <kalle.valo@iki.fi>,
	Oliver Hartkopp <socketcan@hartkopp.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: mac80211: NOHZ: local_softirq_pending 08
Date: Wed, 30 Sep 2009 17:10:28 +0200	[thread overview]
Message-ID: <200909301710.31082.mb@bu3sch.de> (raw)
In-Reply-To: <1254322466.3959.5.camel@johannes.local>

On Wednesday 30 September 2009 16:54:26 Johannes Berg wrote:
> On Wed, 2009-09-30 at 17:47 +0300, Kalle Valo wrote:
> 
> > I agree with Michael. The bug is real and I have verified that
> > Michael's patch fixes the issue. Better to apply the patch now, it's
> > trivial to change the implementation if/when the network stack has
> > support for this.
> 
> FWIW, I think in mac80211 the in_interrupt() check can never return true
> since we postpone all RX to the tasklet. But the tasklet seems to be ok
> -- so should it really be in_interrupt()?

I think a tasklet is also in_interrupt(), because it's a softirq.
in_interrupt() returns false in process context. The problem appeared when
the b43 driver started passing RX frames while being in process context (threaded IRQ).
It previously was in tasklet (= softirq) context.

-- 
Greetings, Michael.

  reply	other threads:[~2009-09-30 15:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 14:48 mac80211: NOHZ: local_softirq_pending 08 Michael Buesch
2009-09-11 14:57 ` Kalle Valo
2009-09-11 15:07   ` Michael Buesch
2009-09-11 16:07     ` Kalle Valo
2009-09-11 16:07     ` Oliver Hartkopp
2009-09-11 16:13       ` Michael Buesch
2009-09-12 16:41         ` Oliver Hartkopp
2009-09-12 16:51           ` Michael Buesch
2009-09-12 18:07             ` Oliver Hartkopp
2009-09-29 19:29           ` John W. Linville
2009-09-30 11:56             ` Oliver Hartkopp
2009-09-30 14:33               ` Michael Buesch
2009-09-30 14:47                 ` Kalle Valo
2009-09-30 14:54                   ` Johannes Berg
2009-09-30 15:10                     ` Michael Buesch [this message]
2009-09-30 15:21                       ` Johannes Berg
2009-09-30 17:51                         ` Oliver Hartkopp
2009-09-30 18:18                           ` [PATCH] net: fix " Oliver Hartkopp
2009-09-30 18:47                             ` John W. Linville
2009-09-30 23:33                             ` David Miller
2009-10-01  7:08                               ` Oliver Hartkopp
2009-10-01 14:04                               ` Michael Buesch
2009-10-01 14:24                                 ` Kalle Valo
2009-10-01 18:42                                 ` Johannes Berg
2009-10-01 19:10                                   ` Michael Buesch
2009-10-01 19:26                                     ` Johannes Berg
2009-10-01 19:32                                     ` David Miller

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=200909301710.31082.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=johannes@sipsolutions.net \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    /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).