From: Tejun Heo <tj@kernel.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Joe Lawrence <joe.lawrence@stratus.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>,
Jouni Malinen <jouni@qca.qualcomm.com>,
Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>,
Senthil Balasubramanian <senthilb@qca.qualcomm.com>,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: stop_machine lockup issue in 3.9.y.
Date: Thu, 6 Jun 2013 14:17:52 -0700 [thread overview]
Message-ID: <20130606211752.GG5045@htj.dyndns.org> (raw)
In-Reply-To: <51B0FBFC.8040809@candelatech.com>
On Thu, Jun 06, 2013 at 02:15:40PM -0700, Ben Greear wrote:
> >First of all, kudos for tracking the issue down. While the removal of
> >looping limit in softirq handling was the direct cause for making the
> >problem visible, it's very bothering that we have softirq runaway.
> >Finding out the perpetrator shouldn't be hard. Something like the
> >following should work (untested). Once we know which softirq (prolly
> >the network one), we can dig deeper.
>
> The patch below assumes my fix is not in the code, right?
Yeap.
> I'll work on this, but it will probably be next week before
> I have time...gotta catch up on some other things first.
Thanks a lot for hunting this down!
--
tejun
next prev parent reply other threads:[~2013-06-06 21:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51A8E884.1080009@candelatech.com>
[not found] ` <87ehclumhr.fsf@rustcorp.com.au>
[not found] ` <alpine.DEB.2.02.1306022212200.10003@jlaw-desktop.mno.stratus.com>
[not found] ` <alpine.DEB.2.02.1306030724230.19647@jlaw-desktop.mno.stratus.com>
2013-06-03 14:17 ` Please add to stable: module: don't unlink the module until we've removed all exposure Joe Lawrence
2013-06-03 15:59 ` Ben Greear
2013-06-03 16:36 ` Ben Greear
2013-06-04 4:37 ` Rusty Russell
2013-06-04 5:56 ` Rusty Russell
2013-06-04 14:07 ` Joe Lawrence
2013-06-04 16:50 ` Joe Lawrence
2013-06-04 16:53 ` Ben Greear
2013-06-04 17:45 ` Ben Greear
2013-06-05 4:17 ` Rusty Russell
2013-06-05 7:15 ` Tejun Heo
2013-06-05 16:59 ` Ben Greear
2013-06-05 18:48 ` Tejun Heo
2013-06-05 19:11 ` Ben Greear
2013-06-05 19:31 ` stop_machine lockup issue in 3.9.y Ben Greear
2013-06-05 20:58 ` Ben Greear
2013-06-05 21:11 ` Tejun Heo
2013-06-05 21:33 ` Ben Greear
2013-06-06 1:34 ` Eric Dumazet
2013-06-06 3:14 ` Tejun Heo
2013-06-06 3:26 ` Eric Dumazet
2013-06-06 3:41 ` Ben Greear
2013-06-06 3:46 ` Eric Dumazet
2013-06-06 3:50 ` Ben Greear
2013-06-06 4:08 ` Eric Dumazet
2013-06-06 20:55 ` Tejun Heo
2013-06-06 21:15 ` Ben Greear
2013-06-06 21:17 ` Tejun Heo [this message]
2013-06-05 3:29 ` Please add to stable: module: don't unlink the module until we've removed all exposure Rusty Russell
2013-06-05 5:07 ` Greg KH
2013-06-05 7:13 ` Rusty Russell
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=20130606211752.GG5045@htj.dyndns.org \
--to=tj@kernel.org \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=eric.dumazet@gmail.com \
--cc=greearb@candelatech.com \
--cc=joe.lawrence@stratus.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@qca.qualcomm.com \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=senthilb@qca.qualcomm.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vthiagar@qca.qualcomm.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