linux-kernel - Re:Re: [PATCH] kernel/hung_task: Add a whitelist and blacklist mechanism.

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] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 19 Apr 2021 09:46:26 +0800 (GMT+08:00)
From:   周传高 <zhouchuangao@...o.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Ingo Molnar <mingo@...hat.com>, Juri Lelli <juri.lelli@...hat.com>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Dietmar Eggemann <dietmar.eggemann@....com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
        Daniel Bristot de Oliveira <bristot@...hat.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Kees Cook <keescook@...omium.org>,
        Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
        Michal Hocko <mhocko@...e.com>,
        "Guilherme G. Piccoli" <gpiccoli@...onical.com>,
        Vlastimil Babka <vbabka@...e.cz>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re:Re: [PATCH] kernel/hung_task: Add a whitelist and blacklist mechanism.


>On Sat, Apr 17, 2021 at 07:13:01AM -0700, zhouchuangao wrote:
>> eg:
>> In Android system, we usually and some processes to the whitelist.
>> static task_t task_whitelist[] = {
>> 	{"mdrt_thread", HUNG_TASK_WHITELIST},
>> 	{"chre_kthread", HUNG_TASK_WHITELIST},
>> 	{"scp_power_reset", HUNG_TASK_WHITELIST},
>> 	{"ccci_fsm1", HUNG_TASK_WHITELIST},
>> 	{"qos_ipi_recv", HUNG_TASK_WHITELIST},
>> 	{NULL, 0},
>> };
>
>What are these tasks doing that the hung-task detector fires on them?
>Should you fix that instead?

These tasks are implemented by the SoC vendor, and normally they do
not configure HUNG TASK, so we need to ignore these tasks if we use
HUNG TASK. 
Here I want to provide a ignorelist and fatallist mechanism, different
users or use scenarios can be modified accordingly. 
The default ignorelist or fatallist is empty.

Thanks,
zhouchuangao