linux-kernel - [/proc/vmstat] nr_kernel_stack is actually meminfo_kernel_stack

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

Date:   Tue, 27 Dec 2022 20:09:11 +0800 (CST)
From:   "David Wang" <00107082@....com>
To:     linux-kernel@...r.kernel.org
Subject: [/proc/vmstat] nr_kernel_stack is actually meminfo_kernel_stack_kb?
 why...

Hi, 

The nr_kernel_stack in /proc/vmstat now is the same as KernelStack /proc/meminfo, and has been this way since a change made six years ago (https://lore.kernel.org/lkml/24279d4009c821de64109055665429fad2a7bff7.1466036668.git.luto@kernel.org/) 

The situation now is very confusing:
1. the naming should be changed, how could one take 'nr_kernel_stack' as a naming for meminfo-KernelStack-KB?
2. Dose kernel.threads-max now means kernel.threads-max-kB?

3. I really think the number of threads currently running in the system is a very usful stastistic, I used to collect nr_kernel_stack in /proc/vmstat to monitor thread/task usage in the system,  and trigger alarm when nr_kernel_stack is approaching somewhere near kernel.threads-max.  

Hope things can be changed, and nr_kernel_stack could be restored/fixed to its old meaning.

David