From: Ben Greear <greearb@candelatech.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v2] Fix lockup related to stop_machine being stuck in __do_softirq.
Date: Thu, 06 Jun 2013 14:33:23 -0700 [thread overview]
Message-ID: <51B10023.3050400@candelatech.com> (raw)
In-Reply-To: <20130606204821.GB5045@htj.dyndns.org>
On 06/06/2013 01:48 PM, Tejun Heo wrote:
> As wrote before, a brief explanation on why both are necessary would
> be nice. Something like - "the time limit prevents from introducing
> excessive latency from softirq handling and the loop limit protects
> against softirq runaway which may happen during stop_machine - see
> XXX".
>
> Please cc Linus and also cc stable@vger.kernel.org. We definitely
> want this backported.
v3 was sent, with updated comments and expanded CC list.
The patch is against 3.9.4, though I assume it will apply
to the upstream kernel easily enough.
I didn't want to add a link to the email thread.. The commit message
and patch has enough info that I think an interested party could find
the email thread easily enough if they needed more history.
And, much of the email thread is me running in circles thinking
I am going insane :)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2013-06-06 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 16:10 [PATCH v2] Fix lockup related to stop_machine being stuck in __do_softirq greearb
2013-06-06 16:14 ` Eric Dumazet
2013-06-06 20:48 ` Tejun Heo
2013-06-06 21:33 ` Ben Greear [this message]
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=51B10023.3050400@candelatech.com \
--to=greearb@candelatech.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.