linux-kernel - Re: [PATCH 1/2] docs: admin-guide: Fix min value of threads-max in kernel.rst

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: <20191105063008.GC22672@dhcp22.suse.cz>
Date:   Tue, 5 Nov 2019 07:30:08 +0100
From:   Michal Hocko <mhocko@...nel.org>
To:     Masanari Iida <standby24x7@...il.com>
Cc:     linux-kernel@...r.kernel.org, ebiederm@...ssion.com,
        akpm@...ux-foundation.org, stable@...r.kernel.org, corbet@....net,
        linux-doc@...r.kernel.org, mingo@...hat.com
Subject: Re: [PATCH 1/2] docs: admin-guide: Fix min value of threads-max in
 kernel.rst

On Fri 01-11-19 13:04:37, Masanari Iida wrote:
> Since following patch was merged 5.4-rc3, minimum value for
> threads-max changed to 1.
> 
> kernel/sysctl.c: do not override max_threads provided by userspace
> b0f53dbc4bc4c371f38b14c391095a3bb8a0bb40
> 
> Signed-off-by: Masanari Iida <standby24x7@...il.com>

Acked-by: Michal Hocko <mhocko@...e.com>

> ---
>  Documentation/admin-guide/sysctl/kernel.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index 032c7cd3cede..38e0f10d7d9f 100644
> --- a/Documentation/admin-guide/sysctl/kernel.rst
> +++ b/Documentation/admin-guide/sysctl/kernel.rst
> @@ -1101,7 +1101,7 @@ During initialization the kernel sets this value such that even if the
>  maximum number of threads is created, the thread structures occupy only
>  a part (1/8th) of the available RAM pages.
>  
> -The minimum value that can be written to threads-max is 20.
> +The minimum value that can be written to threads-max is 1.
>  
>  The maximum value that can be written to threads-max is given by the
>  constant FUTEX_TID_MASK (0x3fffffff).
> -- 
> 2.24.0.rc1

-- 
Michal Hocko
SUSE Labs