lkml.org 
[lkml]   [2017]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] hung task: check specific tasks for long uninterruptible sleep state
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.

\
 
 \ /
  Last update: 2017-11-09 00:45    [W:0.056 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site