linux-kernel - Re: [PATCH] workqueue: Fix cpu_intensive_thresh

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]

Message-ID: <23267466-dc1e-5f39-ce6c-45f0f61f281c@infradead.org>
Date:   Tue, 11 Jul 2023 07:50:14 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Geert Uytterhoeven <geert+renesas@...der.be>,
        Tejun Heo <tj@...nel.org>,
        Lai Jiangshan <jiangshanlai@...il.com>,
        Peter Zijlstra <peterz@...radead.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] workqueue: Fix cpu_intensive_thresh_us name in help text



On 7/11/23 03:38, Geert Uytterhoeven wrote:
> There exists no parameter called "cpu_intensive_threshold_us".
> The actual parameter name is "cpu_intensive_thresh_us".
> 
> Fixes: 6363845005202148 ("workqueue: Report work funcs that trigger automatic CPU_INTENSIVE mechanism")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>

Reviewed-by: Randy Dunlap <rdunlap@...radead.org>

Thanks.

> ---
>  lib/Kconfig.debug | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index c8371502b4b2e678..5da00849edebafdd 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1200,7 +1200,7 @@ config WQ_CPU_INTENSIVE_REPORT
>  	help
>  	  Say Y here to enable reporting of concurrency-managed per-cpu work
>  	  items that hog CPUs for longer than
> -	  workqueue.cpu_intensive_threshold_us. Workqueue automatically
> +	  workqueue.cpu_intensive_thresh_us. Workqueue automatically
>  	  detects and excludes them from concurrency management to prevent
>  	  them from stalling other per-cpu work items. Occassional
>  	  triggering may not necessarily indicate a problem. Repeated

-- 
~Randy