From: Simon Kirby <sim@hostway.ca>
To: Andi Kleen <ak@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hung task detector versus NFS (TASK_KILLABLE)
Date: Wed, 9 Mar 2016 12:23:16 -0800 [thread overview]
Message-ID: <20160309202316.GA21640@hostway.ca> (raw)
In-Reply-To: <20160308031119.GM23621@tassilo.jf.intel.com>
On Mon, Mar 07, 2016 at 07:11:19PM -0800, Andi Kleen wrote:
> > I write this because I would actually find it useful to see the original
> > backtrace, even if it is interruptible, not just the collateral damage.
> > Since the "skipping" of NFS is basically incomplete anyway, how big a
> > deal is this "feature"?
>
> Random backtrace spewing is always a misfeature for 99.99+% of the users
> for whom it is gibberish.
Distributions all seem to ship with it on because apparently some people
can read it. There was even discussion that the default 10 is not enough.
> If you really need it yourself add a kprobe.
To emulate a hung task backtrace even when TASK_KILLABLE? That sounds
like some hoop-jumping, but I don't know kprobes.
I'm just saying the current "NFS filter" is broken ("cat a" twice), but
this really will make more noise for people (in cases where NFS is stuck
for minutes), I guess I'll just sit in a corner with that line changed in
my tree.
Simon-
prev parent reply other threads:[~2016-03-09 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 23:59 Hung task detector versus NFS (TASK_KILLABLE) Simon Kirby
2016-03-08 3:11 ` Andi Kleen
2016-03-09 20:23 ` Simon Kirby [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=20160309202316.GA21640@hostway.ca \
--to=sim@hostway.ca \
--cc=ak@linux.intel.com \
--cc=linux-kernel@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