All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: akpm@linux-foundation.org
Cc: adobriyan@gmail.com, ebiederm@xmission.com,
	keescook@chromium.org, mm-commits@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: + pid-delete-reserved_pids.patch added to -mm tree
Date: Tue, 3 Oct 2017 17:53:15 +0200	[thread overview]
Message-ID: <20171003155314.GA9929@redhat.com> (raw)
In-Reply-To: <59d2c819.FeJw+478bpKqle6W%akpm@linux-foundation.org>

Hi Alexey,

On 10/02, Andrew Morton wrote:
>
> From: Alexey Dobriyan <adobriyan@gmail.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.

  reply	other threads:[~2017-10-03 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02 23:13 + pid-delete-reserved_pids.patch added to -mm tree akpm
2017-10-03 15:53 ` Oleg Nesterov [this message]
2017-10-03 21:53   ` Alexey Dobriyan
2017-10-04 16:36     ` Oleg Nesterov
2017-10-04 20:12       ` Alexey Dobriyan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171003155314.GA9929@redhat.com \
    --to=oleg@redhat.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.