From: Andrew Morton <akpm@linux-foundation.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: clingutla@codeaurora.org, kimran@codeaurora.org,
mingo@kernel.org, peterz@infradead.org, mcgrof@kernel.org,
keescook@chromium.org, shile.zhang@nokia.com,
matt@codeblueprint.co.uk, vegard.nossum@oracle.com,
jsiddle@redhat.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] hung task: check specific tasks for long uninterruptible sleep state
Date: Wed, 8 Nov 2017 15:44:29 -0800 [thread overview]
Message-ID: <20171108154429.909e12c5f7141cde37416469@linux-foundation.org> (raw)
In-Reply-To: <201711082057.IDF56726.OMHOSFVFJtQOFL@I-love.SAKURA.ne.jp>
On Wed, 8 Nov 2017 20:57:42 +0900 Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> wrote:
> Lingutla Chandrasekhar wrote:
> > Some tasks may intentionally moves to uninterruptable sleep state,
> > which shouldn't leads to khungtask panics, as those are recoverable
> > hungs. So to avoid false hung reports, add an option to select tasks
> > to be monitored and report/panic them only.
>
> What are backtraces of such tasks? Please point the locations in the code.
>
> If they are absolutely recoverable, why can't we let themselves declare that
> "I'm intentionally in uninterruptible state. But there is no dependency that
> prevents me from recovering. So, please ignore me." using per "struct
> task_struct" flags rather than introducing userspace controlled interface?
Yes. Please tell us much much much more about the use case and
scenarios which inspired this change.
next prev parent reply other threads:[~2017-11-08 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 10:25 [PATCH] RFC: hung task: Check " Imran Khan
2017-08-22 1:54 ` Zhang, Shile (NSB - CN/Hangzhou)
2017-08-22 6:03 ` Imran Khan
2017-08-22 6:49 ` Zhang, Shile (NSB - CN/Hangzhou)
2017-08-22 20:36 ` Peter Zijlstra
2017-08-23 12:25 ` Imran Khan
2017-11-08 6:28 ` [RFC] hung task: check " Lingutla Chandrasekhar
2017-11-08 11:57 ` Tetsuo Handa
2017-11-08 23:44 ` Andrew Morton [this message]
2017-11-09 1:54 ` Luis R. Rodriguez
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=20171108154429.909e12c5f7141cde37416469@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clingutla@codeaurora.org \
--cc=jsiddle@redhat.com \
--cc=keescook@chromium.org \
--cc=kimran@codeaurora.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peterz@infradead.org \
--cc=shile.zhang@nokia.com \
--cc=vegard.nossum@oracle.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
all inboxes | Powered by JetHome®