From: Peter Zijlstra <peterz@infradead.org>
To: liyueyi <liyueyi@live.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
liyueyi <liyueyi@xiaomi.com>
Subject: Re: [PATCH] kthread: set kthread state to TASK_IDLE.
Date: Wed, 1 Apr 2020 11:39:04 +0200 [thread overview]
Message-ID: <20200401093904.GX20713@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <DM6PR11MB3531D3B164357B2DC476102DDFC90@DM6PR11MB3531.namprd11.prod.outlook.com>
On Wed, Apr 01, 2020 at 02:52:15PM +0800, liyueyi wrote:
> From: liyueyi <liyueyi@xiaomi.com>
>
> Currently kthread() sleeps in TASK_UNINTERRUPTIBLE state waiting
> for the first wakeup, it may be detected by DETECT_HUNG_TASK if
> the first wakeup is coming later. Since kernel has introduced
> TASK_IDLE, change kthread state to TASK_IDLE.
How the heck can that ever happen anyway? Is this some virt
brain-damage?
And how is it not a real problem when it takes this long?
next prev parent reply other threads:[~2020-04-01 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 6:52 [PATCH] kthread: set kthread state to TASK_IDLE liyueyi
2020-04-01 9:39 ` Peter Zijlstra [this message]
[not found] ` <DM6PR11MB3531904888FBD86F4ED43009DFC90@DM6PR11MB3531.namprd11.prod.outlook.com>
2020-04-01 11:12 ` Peter Zijlstra
2020-04-01 12:27 ` Yueyi Li
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=20200401093904.GX20713@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liyueyi@live.com \
--cc=liyueyi@xiaomi.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;
as well as URLs for NNTP newsgroup(s).