linux-kernel - Re: [PATCH] kthread: set kthread state to TASK

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20200401093904.GX20713@hirez.programming.kicks-ass.net>
Date:   Wed, 1 Apr 2020 11:39:04 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     liyueyi <liyueyi@...e.com>
Cc:     gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
        liyueyi <liyueyi@...omi.com>
Subject: Re: [PATCH] kthread: set kthread state to TASK_IDLE.

On Wed, Apr 01, 2020 at 02:52:15PM +0800, liyueyi wrote:
> From: liyueyi <liyueyi@...omi.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?