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-next>] [day] [month] [year] [list]
Date:   Tue, 3 Oct 2017 17:53:15 +0200
From:   Oleg Nesterov <oleg@...hat.com>
To:     akpm@...ux-foundation.org
Cc:     adobriyan@...il.com, ebiederm@...ssion.com, keescook@...omium.org,
        mm-commits@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: + pid-delete-reserved_pids.patch added to -mm tree

Hi Alexey,

On 10/02, Andrew Morton wrote:
>
> From: Alexey Dobriyan <adobriyan@...il.com>
> Subject: pid: delete RESERVED_PIDS
>
> RESERVED_PIDS had a noble goal: to protect root from PID exhaustion since
> at least ~2.5.40

I am just curious, where did you find the change which documents this goal?

> except it never did that because there was no capability
> or uid checks.
>
> Allow small pids to be allocated after rollover, there is nothing sacred
> about them.
>
> Resource exhaustion should be handled by rlimits and/or kernel memory
> accounting.

I won't argue, but I always thought that the only purpose of RESERVED_PIDS
is to make the system/kernek daemons started at boot time more "visible" in
/usr/bin/ps output.

Oleg.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ